Java Thrown Back in Windows, For Now

darnellmc writes: "According to this News.com article, Microsoft has decided to include their JVM in the next Windows XP service pack. They are doing this in an attempt to avoid Sun's recent lawsuit against them for anti-trust violations. I wonder if the recent decision allowing the nine states' suit to continue had anything to do with this? Of course it did. MS plans not to have the JVM in future versions of Windows though."

Comments

Nothing like those temporary compromises

[newt_sd]

Hmmm, When are we gonna start learning from Microsoft. Do what ever you want and piss on the competition and be rewarded in Monopoly land. Looks like they own park place and we are struggling down on Baltic Ave.

BIG FAT HAIRY DEAL

[furiousgeorge]

I'm sure i'll get modded down, but whatever.

If you've ever used XP things are pretty damn simple. Go to a site that uses java .... up pops a window saying "you need a java VM - wanna download one?" Say yes --- it's downloaded from MS and life goes on. Same thing with flash or a bazillion other plugins.

Java was never 'blocked' or 'disabled'. They just didn't ship it on the CD's.

Christ -- don't we have anything REALLY important to report on?

Re:Hmm...

[ScottKin]

All of the warez-monkeys that posted copies of Win9x along with CD Keys on pr0n-filled W@R3Z S|73Z kinda forced the issue. I'm thankfull that I got the opportunity to help close some of them down.

ScottKin

Re:the MS JVM

[hendridm]

> when it crashes, it crashes hard, and geez, what crashes.

Ummm, try upgrading from Windows 98 to something like Windows 2000 or XP.

Oh yeah, and throw away that AMD crap while you're at it and don't buy memory from the cheapest person on Pricewatch. I have ZERO problems with my 5 installations of Windows 2000 Professional (one game machine, one general machine, and 3 development/testing/network slaves). Intel CPUs/boards/NIC, Kingston or Crucial memory. You get what you pay for.

Re:Come on...

[MisterBlister]

I hardly think Sun needs Microsoft's help when it comes to confusing the user and breaking Java apps. Have you ever tried using even Sun's own implementation of Java? Slow as fuck. Buggy as fuck. Java's OK on the server where workarounds for the shady concept of WORA can be implemented, but it sucks ass as a client-side language.

The most ironic part is even though Microsoft DID pull some shady tricks with their JVM implementation, it was by far the best JVM to run client-side apps on, bar none. Even when running pure Java (non-MS extended) apps you didn't have to sit there waiting 20 minutes looking at a blank gray box while the JVM initalized, unlike Sun's own VM..

Re:This will hurt Java

[WasterDave]

So, do some Java bunnies want to tell me what happened with "write once, run anywhere"?

Hmmmm?

So why should I believe the next piece of pointless hype?

Dave

Re:Wait, I'm confused...

[drew]

Microsoft has managed to completely destroy any hopes of Java being a great client-side language -- by including an incompatible version of Java, then not including it, and then including that same ancient crappy version again.

actually, i think sun had already pretty much destroyed java's hopes of becoming a great client-side language when they made it suck.