MS Must Ship Java With Windows Within 120 Days
Suppafly writes "Cnet is reporting that a federal judge on Wednesday ordered Microsoft to begin shipping Sun Microsystems' Java with the Windows operating system within 120 days, after the companies fought over implementing a ruling he made last month."
2) Use the Sun JavaPlugin and/or WebStart, that's what they exist for.
I have to side with Microsoft on this one. I don't think the government should have the power to say you must include X in your product. It's like the government mandating that Ford must use Bosch break systems in their vehicles even though Ford can make their own cheaper (purely hypothetical situation). How would everyone like it if the court forced Debian to include Sun's Java as part of the standard install instead of the user having the option to install gcj for instance?
"Nature doesn't care how smart you are. You can still be wrong." - Richard Feynman
... I don't agree with the ruling ...
....
... or why don't they have to include the Macromedia plug-in?
... this is my opinion in regards to fair competition
It is like telling AOL to ship MSN8 with their latest distro
Sun and Microsoft are competitors. MS developes Visual Studio and should promot their programming distro.
If MS has to include Java, wh don't the have to include Perl, Python, PHP, and interpreters for other languages
Everyone has to download the pluins and interpreters for other products, why should Java and Sun be so special?
BTW: My favorite programming language is Java, so I am definately not biased here
HallmarkOrnaments.Com
"If my order doesn't get stayed or reversed (on appeal), it's going to get done," Motz said.
Anyone else read this and get the impression that Motz isn't particularly confident that it will happen? I read that line and my brain converted it to: "If Microsoft doesn't mind and decides not to take their money and lawyers to a more friendly court farther up stream then it's going to get done, but don't count on it."
Appended to the end of comments you post. 120 chars.
http://java.sun.com/getjava/index.html
You know what, you're absolutely right.
is exactly the same as Thank you for clearing that up.Yes, I'm still a junky. Are you still a bitch?
What microsoft is doing is more akin to the phone company, a legally acknowledged monopoly, that blocks you from calling a competitor of theirs. Except in microsoft's case, they reroute the call to a mock phone company which provides different rates and services intentionally meant to dissaude people from switching to that competitor.
It's anti-competive. It's illegal. And this is a fair punishment.
Javascript and Java have *nothing* to do with each other.. nothing at all. This is like comparing Javascript to TCL. Or C.
Applets? It's about more than applets. Java applets are a niche? I use some daily in my work, and I *need* them, and it's a pain in the ass when microsoft made using java difficult. It USED to be easy.
Javascript developers? Who are you kidding? Javascript is a joke.
Don't compare them. Don't contrast them. That's like comparing Apples to Moonrocks.
Correct me if I am wrong, but didn't Sun start out suing MS to _remove_ Java from Windows, then sue to get it back in, and so on? A few times back and forth?
That's sort of obnoxious, like having a little brother with ADD and a mean streak.
jack's bicycle is music to my ears
I think this is excellent news; as a developer, the fact that java is not shipped with windows makes it a pain in the ass to write java apps for windows users. :)
if i write a c++ app, no problem, a user can simply download and run it. If i write a java app, and say distribute it as a JAR file, your average user isnt gonna want to download the Java runtime or sdk, then launch the jar file calling java -jar or javaw.exe or whatever.
Java pre installed on windows means i can easily write pure java apps that will work easily on all windows boxes. Bring it on
RJ
Last.fm - join the social music revolution
It's not about preinstall. It's about the fact that M$ deliberately includes an outdated & mangled (something like 5 years now) version of Java to make it look bad.
Java and Linux are threat to microsoft, so it's good for M$ when another frustrated users curses 'that fu**ing java' again when it crashes on microsoft's ancient runtime.
Think it like this: how would you feel if all the games would preinstall some buggy old beta version of the display driver for the hardware that your company is manufacturing. If you do this, you should at least inform the users that something better is available.
Funny, if I click to open a pdf-document (without acroreader installed) my XP offers to search the right tool from the internet. I think it should behave the same way if double click on that *.jar - package.
No matter how fast light travels it finds the darkness has always got there first, and is waiting for it. (T. Pratchett)
I never lost the 'right' to use Java on windows.
This is about MS's rights in the marketplace, not my rights online.
Or does anything that has to do with MSFT automatically categorize it as YRO to get peoples dander up?
I don't need no instructions to know how to rock!!!!
Installing Java is not the issue. They provided tools to their customers that rely on their VM being present for their corporate web pages to function. I know this because the company I am currently doing contract work for has a web application they purchased for content management of their shared project/business documents. It is written using Microsoft tools, and won't work if you have the Sun VM activated for your browser.
Their argument is valid, that this will cause problems for their corporate clients. It will cause problems whenever it comes out, because some of their corporate clients (or their customers) will not be able to view their web pages properly.
Delaying this rollout is not really going to help much, because most web application get updated when the application changes, not when the client changes. Their corporate customers are going to be very angry with them about this kind of problem.
I don't feel sorry for Microsoft, because they got themselves into this mess by trying to spin Java out of Suns control, and make it into a Microsoft specific version. Now they have been told to live up to their contract with Sun, and must pay the price for their behavior. I do feel sorry for their corporate customers who bought into systems designed around the Microsoft VM, because they were dumb, not culpable. They will end up paying part of the price for Microsoft's past errors.
Most corporate clients will have control of their desktops, and can make their internal users use the Microsoft VM until they can fix things. They can't make joe user on the internet do that, which is where things will break down.
Suns JVM is the ONLY... PROGRAM... EVER... To cause my 512 meg windows machine with 752 meg of VM popup and say "Windows is increasing your windows VM" when running a tiny editing program. Every single actual java program I have ever run using Suns JVM has been buggy and slow. It turns a p4 2.5 gig machine into a 486. It's the crappiest piece of junk I have ever been forced to install on a Windows box (And I've been forced to install both Quicktime AND Real multiple times), and now the entire world has to suffer having it.
Microsoft's JVM was 4x faster and less buggy that Suns. It was SO FAST, that sun had to rig one of their benchmarking programs to hide the fact!
Sun screwed themselves over by being lazy and stupid with their poor JVM implentation and lousy development tools. 4 years later, Sun's Java on the desktop is still a piece of crap. Java could have been something if Sun had had any balls and/or brains. But they have neither and they destroyed their chance.
Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
By reading the threads in this article it is obvious that:
Microsoft = Bad
Sun/Java = Good
But have you all forgotten that Sun reneged on ISO standardization of Java. Isn't that a bad thing? After promising ISO compliance as a means of getting the developers hooked, shouldn't Sun and Java be looked upon with scorn? All you Java developers are locked into a proprietary platform. How is that any different from riding the Microsoft trolley?
The anti-Microsoft stuff is getting ridiculous. It is just plain pathetic when it becomes hypocritical. Mod me down all you want, troll, flamebait, whatever. Some of you need to take a step back and assess your priorities.
Your post is so full of misinformation I don't know where to start.
JavaScript is a client side SCRIPTING language, which has nothing to do with Java. (JavaScript's author, Netscape, decided to cash in on Java's rising popularity by hikacking its name) It does very SIMPLE things through your browser. It has NOT been "overwhelmingly chosen [...] for advanced web-based functionality". Where do you get this stuff?
There are no such thing as "JavaScript developers" anymore than there are "Logo developers". There are web developers who have some scripting skills, and there are real coders who use JavaScript for basic, limited stuff. Advanced client side tasks require something like a Java applet. These are everywhere. Nobody "switches" from JavaScript to Java, the very concept is absurd. They are not designed for the same tasks.
There is huge demand for Java development right now. It is not a niche, it is at the forefront of the mainstream. For desktop apps, AWT is dead and has been for quite a while. Swing 1.3+ is very lightweight and fast, if you know how to code it efficiently. Our company has written many Java desktop apps. Way faster to write than C++ and far less bug prone. And the compiled code will run identically everywhere.
One thing you don't mention at all is Server side apps. Java is kicking ass in this arena and has been for years.
If you read the article, you'd notice it said that Microsoft has been ordered "to begin shipping Sun Microsystems' Java". Not implement their own version. So they won't be tainting it... although they will likely add as much hassle as they can to using it, like not installing it by default.
"Mind, as manifested by the capacity to make choices, is to some extent present in every electron." -Freeman Dyson
You're right - it is a bad thing that the program you have to support was developed for Microsoft's broken implementation only. But don't make the world pay for this mistake by asking for that broken implementation the standard.
Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.
As part of their contract, MS was forbidden to add public names to system packages (e.g. java.lang, java.net, etc). Nevertheless, they did so. There were some stretchers on both sides.
Microsoft PR claimed that Sun was forbidding them to add Windows specific extensions. This was silly - there was no problem with any number of packages named com.ms.* or whatever (except that the ms.com domain belongs to Morgan Stanley, and thus didn't follow the 3rd party naming convention - but that wasn't in the contract). There were some very nice extensions with proper names - like JDirect which let you call Microsoft DLL's without writing JNI glue. The problem was that Microsoft wanted to name some extensions java.*. This would of course cause the unwary programmer to inadvertantly create Java programs which only run on Windows - despite not knowingly using any MS specific packages. Exactly what MS wanted.
On Sun's part, the contract included a list of packages which Microsoft could not touch the public name space of. More system packages were added to Java 1.1. Sun claimed that Microsoft couldn't touch those either - reasonable, but they weren't in the specific list in the contract.
The completeness problem was along the same lines. Microsoft provided a complete 1.0 API. However, they left out components of the 1.1 API that competed with their own offerings. For instance, they left out RMI and offered DCOM support instead. Sun said that it was understood that the same restrictions regarding system name space pollution and completeness would apply to the packages of subsequent API versions. But this was not spelled out in the contract. It would not be in the ruthless spirit of Microsoft for them to follow the spirit of a contract if they could find a loophole.
Regardless of quibbling over whether the system package list under contract should expand to match new API versions, Microsoft polluted even core packages from 1.0 with handy additions sure to entice the unwary. So they were guilty even by the letter of the law.
Java has become one of the primary tools for enterprise development, mostly on the server, but also on enterprise clients, where downloading an applet or java app is typically not time consuming for the client because they are on a LAN.
What takes so long in software development? TESTING, and in java testing different versions of the VM. Up until this point, enterprises have been able to enforce a VM version on enterprise clients, and the developers can count on that version being on the client desktops. Now what? If the enterprise wants to stick with its 1.2.2 or 1.3.1 VM, they can't install WinXP SP2? What happens with the next SP and a new java VM? All enterprise java apps will need to be thoroughly tested with each new service pack, since Sun's VMs are not all backwards compatible.
In addition, if anyone is still righting java applets for the internet, how does this help? What percentage of users are going to have XP SP2 in the next 12-24 months?
This solves none of the Java VM version issues. This was Sun saying "wah wah" in court and getting a sympathetic judge.
Sun needs to hand over Java to the JCP and stop using it as a weapon in its fight against MS.
It's clear that so many of you have NO idea what this is about.
Sun and MS (sorry, M$) had an agreement where Microsoft would include a Java runtime with Windows. Only M$ made their own VM/runtime that was 'tweaked' and extended with extra functionality that ONLY worked under Windows.
Sun complained that this implementation was NOT Java, because it didn't match the Java specs. So they got a court to make MS remove their non-standard non-Java Java VM from Windows. But they didn't replace it with a fully-functionaly VM - they replaced it with nothing, contrary to their agreement with Sun.
So all Sun is doing is getting their agreement with MS enforced by a court. This has NOTHING to do with MS being a monopoly or Sun wanting their VM on Windows or anything like that. It comes down to MS creatively breaking a contract in order to kill Java (by nullifying it's main goal of platform-independence) and replace it with C#.
So please, no more posts about "But they wanted MS to remove IE, now they're adding Java?!?" or "This is okay because MS is a monopoly". Go start a thread elsewhere if you want to bitch about it, instead of crapping on about MS abusing their position as monopoly in every Slashdot article. Fuck off.
Ignore the ruling. What are the courts going to do, issue another ruling that says, "we really mean it this time?"
Probably first there would be essentially an ultimatum, yes. Beyond that, start putting people in prison for contempt of court. Board level people I would imagine.
The poster said he has to support an app that is written to "real" Java, and on Windows systems the poster has to walk users through downloading and installing a "real" JVM (from Sun)because MS's is garbage.
Actually, in previous stages of this case Sun got an order forbidding MS from including Java because MS was bastardizing it (with "Java Foundation Classes" wrappers for MFC). Then they "settled" and agreed to let MS include Java, but only version 1.1.3. This was when the current version was 1.3 at least. So the most recent MS JVM is at least four years behind the times.
The problem with MS'Java is not that it isn't real Java, but that it's woefully outdated. Therefore, users can only run old-style Java software, which is severely limited compared to what can be done with Java today.
A good analogy would be some imaginary operating system promising Windows compatibility, but when you actually try it, you find it only supports Windows up to 3.1. Well Windows has changed an awful lot since then, and Java has changed similarly between 1.1 and 1.3/1.4.