



MS Must Ship Java With Windows Within 120 Days 579
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."
Its about time (Score:5, Informative)
Re:Its about time (Score:3, Insightful)
2) Use the Sun JavaPlugin and/or WebStart, that's what they exist for.
Re:Its about time (Score:5, Informative)
Re:Its about time (Score:4, Interesting)
We'll see...
Re:Its about time (Score:4, Informative)
http://news.com.com/2100-1001-980631.html
"Both Sun and Microsoft submitted written proposals Monday, suggesting exactly which of Microsoft's software titles would have to carry or support Java, in what timeframe the order would be carried out and other details."
Apparently all we really know yet is the time frame, not yet the specifics of how it will be installed.
Re:Its about time (Score:4, Informative)
Re:Its about time (Score:3, Funny)
Re:Its about time (Score:5, Interesting)
If you're going to write a Java program, then you should write it to run in Java. Not MS' "Java". You should know that by not writing to the standard, you'll end up in trouble. It would be like me writing an app to use undocumented APIs, and then whinging when they're changed. If I'd have used what I was given properly, I would not have gotten into the mess, and I would have no-one to blame but myself.
The fact that you have to support a program that was not written correctly is not our fault or problem. Don't get me wrong, I feel for you, but that doesn't change anything.
MS Java *is* Java, but way outdated (Score:3, Insightful)
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.
Re:MS Java *is* Java, but way outdated (Score:3, Funny)
Stop beating around the bush and just say "Linux". Sheesh.
Re:Its about time (Score:3, Insightful)
Odd... (Score:3, Informative)
Am I wrong?
And if I'm right, is your company just not willing or unable to do the same thing?
Or are you whining because its not preinstalled by M$? Are there not other platforms that do NOT have Java installed by default?
I would guess that there are but M$ is the most common OS used by your end users so you run into this most often.
Re:Odd... (Score:5, Insightful)
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.
Just like the airline wars... (Score:3, Interesting)
Same with Sun - they had to either get MS to completely abandon any fake Java implemetation, or to ship theirs, which is what happened.
Re:Odd... (Score:3, Interesting)
That's because the two VMs are essentially incompatible. IE being the de facto standard web browser, most applet writers make damn sure their applet works with MS's JVM first, then maybe, perhaps Mozilla, if they can be bothered.
And although the majority of applets do work on Moz/Sun, the JVM takes frickin' ages to load for the first time.
Well, of course it takes a while compared to the MS one - it's a hell of a lot bigger! Lots and lots of packages have been added to the API since 1.1.4 (the last version that MS released a VM for, iirc), including the entire Collections API (how anyone can write anything worthwhile without that and not tear their hair out I'll never know...)
Re:Odd... (Score:3, Interesting)
If you did, you would have noticed that it settled all claims between Microsoft and Sun except the antitrust ones. When Microsoft signed off on the settlement, they knew Sun could come back and sue them on antitrust grounds.
Notice the word "allowed" MS was under no legal obligation whatsoever to distribute their version for the full 5 years.
You should read the Judge's opinion to understand his reasoning. When java came out, Microsoft knew it would be a threat to their Window monopoly. However, they had nothing to compete with it. So they entered the contract in order to "pollute" (Microsoft's word, not mine) jave. They added extensions not contained in the spec and their development tools automatically used those extenstions without informing the developers that the resulting code would only work with the windows JVM.
Microsoft achieved their goal. They were able to slow down the adoption of java's acceptence until they couldd come with .NET to compete with Java.
Re:Its about time (Score:2)
Hmm, a major part of the problem is that IE will then go and download an outdated and incompatible version of Java... that Microsoft (it appears) intentionally made that way in order to kill Java...
It certainly won't download Sun's version automatically.
Re:Its about time (Score:3, Informative)
Remember:
unless the software's timestamp is actually changed in that time, the subsequent uses won't repeat the download.
Sun likes to shoot themselves in the foot? (Score:2, Redundant)
Re:Sun likes to shoot themselves in the foot? (Score:5, Interesting)
As for the person that said he would rather have the bastardized version, that is exactly what MS would want people to think. 5 years down the road then, you have half the www sites using the "bastardized" java with stupid calls that cannot be understood by a VM that complies with standards. Sure, its great if you are a windows user, not so great if you are working with *nix like me though.
Once MS is forced to bundle Sun JVM, they will also have to think about coding windows to make it run at a decent speed, else customers will start whining.
Re:Sun likes to shoot themselves in the foot? (Score:3, Informative)
Units??? (Score:5, Funny)
Re:Units??? (Score:2)
120 days = 4 months
since there are (roughly) 4 weeks to a month, that means that
4 months = 16 weeks
Since a fortnight is two weeks, you divide the 16 weeks by 2. Ergo
16 weeks = 8 fortnights.
Whew!
Re:Units??? (Score:2)
And remember, only 17.15 vinals left until Christmas folks!
Re:Units??? (Score:3, Funny)
I would like to help you, but the DCMA forbids me to decipher 120.
Re:Units??? (Score:3, Funny)
This is good news... (Score:5, Informative)
Good news... but kinda irrelevant too... (Score:5, Insightful)
They failed.
Java is more popular than ever. For server-side deployment it's really come into it's own as a cross-platform (dare I say "write once run anywhere") technology. Client level apps (word processors, etc) still have to gain some market acceptance, but overall Java has won acceptance as a viable development and technology platform. Of course, this means to Microsoft that they lost. Now, did MS actually *lose*? Well, in some ways they did, but that's probably best left for another discussion...
Bottom line -- if a Sun-compliant JVM is included with Windows or not, Java solutions will *still* be deployed to Windows systems. Which has continued to be the case for a few years now. It's just going to be a little easier to do the deployment now than before. It doesn't change my job or make it any easier tho...
Re:Good news... but kinda irrelevant too... (Score:3)
Reverse it? Or worsen it? I see nothing in SWT that will change the root problem. And the root problem wasn't swing, and it wasn't Sun either. It was the lack of understanding how to use Swing for UI development in the first place. Sure, Swing is no panecea, and it surely had it's issues to be fixed early on. But if you expect SWT to be the solution then you best be prepared for disappointment.
Slippery slope (Score:2)
Re:This is good news... (Score:3, Informative)
The situation, as I understand, is that the Sun Java VM (hereafter JVM) being removed from the latest versions of Windows (that would be Windows XP) was ruled by the courts to be an anti-competitive measure that allowed Microsoft's use of it's (virtual) monopoly in desktop operating systems to leverage a competitive advantage in another area (this this case, to restrict the proliferation of Java).
The issue, therefore, is not the forced addition of Java into the Windows platform as a new feature (which I would agree would be an issue), but the untimely removal of Java from Windows. The court injuction addresses this issue and promotes choice for software developers.
Re:it's not good news (Score:4, Interesting)
Well, part of the point of the suit is that MS shipped an old, broken VM. Thats partly why Sun sued.
The problem with Microsoft is that they managed to force manufacturers, through contracts, to ship stuff they wanted them to ship. Now Sun is doing the same thing, through the legal system. Sorry, I don't see one as better than the other. Both systems should win or lose on their merits.
Except that MS had already signed a contract to ship a JVM. Sun sued to make them fulfill there contract. Don't really see a problem here, and this certainly isn't the same as MS's dealings with its OEMs.
This ruling is bad news for Java: instead of improving Java sufficiently to be able to compete, Sun will just rely on the legal system to force it on users.
I can't speak for it personally, but it sound like alot of people here think its improved greatly.
Not so fast (Score:5, Interesting)
Microsoft lawyers may be able to either stall it, get it reviewed, or even get it overturned. That's the way the law works. Likewise, there may be other avenues outside of the Courts that Microsoft may take.
This little penguin doesn't forget favors [xnewswire.com]
Re:Not so fast (Score:2)
Such as guerilla commando raids?
Or gorilla [ntk.net] commando raids (Monkey-boy Ballmer leads attack on Sun)?
Or maybe just gorilla Komando [komando.com] raids?
GF.
I feel bad for Microsoft (Score:2, Insightful)
Re:I feel bad for Microsoft (Score:5, Insightful)
However, from what I read earlier on in ths case it is not as simple. What I read was that MS had signed a contract with Sun that they would include Java and then backed out, so I guess this comes down to being the punishment for breach of contract, not just because Sun is whining.
Re:I feel bad for Microsoft (Score:2)
Re: (Score:2)
Re:I feel bad for Microsoft (Score:3, Insightful)
The point is, Microsoft has been convicted of being an illegal monopoly. They have been convicted of breaking a contract with Sun to carry Java. People who do those things don't get to make all their own decisions anymore. Sorry that MS's customers are being hurt by their illegal behavior, but it's not like no one has been saying to dumb MS to avoid these kinds of problems.
Re:I feel bad for Microsoft (Score:2, Insightful)
Comment removed (Score:4, Insightful)
Re: (Score:3, Insightful)
Re:I feel bad for Microsoft (Score:5, Insightful)
A major point of law in the area of monopolies is that a company that has a monopoly in one area can't use that monopoly to build a second monopoly in another area.
M$ was using Java, then dropped Java entirely in order to promote their
By your example, Ford does not need to use Bosch brakes because Ford is an oligopoly, not a monopoly. If Ford, GM, VW, Toyota, etc. decided to start a joint venture to make their own brakes and exclude Bosch, the analogy would be more apt.
The Debian analogy also isn't valid. There are many viable commercial and non-commercial distros. And Debian also doesn't own a competing product.
Re:I feel bad for Microsoft (Score:5, Insightful)
The fact that Microsoft, after bashing Sun's "Network Computers" initiative a few years back, is now coming out with its very own
Oh, and by the way, we're not talking about the Java compiler (which would be comparable to gcj which you mentioned), but about the Java Virtual Machine, which allows Java programs compiled elsewhere to run on your machine.
Daniel
Re:I feel bad for Microsoft (Score:2, Informative)
This is simply not true. The MS VM ran 100% Java Compliant code just fine. The thing MS did as add extensions that were specific to its VM. The Visual J++ tool defaulted to using this extensions. Developers who weren't cafeful could end up writting software that would only run on Windows. But to say that software that was written in pure Java might not work on MS VM is a fallacy.
Re:I feel bad for Microsoft (Score:3, Insightful)
Governments (in theory anyway) are mandated by the people. Who better than the people to decide whether a company has misbehaved and should be ordered to behave differently?
Daniel
Re:I feel bad for Microsoft (Score:3, Informative)
Legally, the only point you make is:
2) Something about the supposed monopoly that Microsoft has, and how bad monopolies are, so this one should be broken as much as possible.
This has little to do with Microsoft's monopoly status. The complaint is that Microsoft signed a contract with Sun to distribute a Sun-certified JVM and Microsoft broke both the spirit and the letter of this agreement. They are now being forced to comply, and rightfully so.
Monopolies have different rules (Score:5, Insightful)
It's anti-competive. It's illegal. And this is a fair punishment.
Re:I feel bad for Microsoft (Score:2)
As I understand it, the issue in this case is that Microsoft signed a contract with Sun some years ago requiring that it implement Java according to Sun specificiations. If this is true (and I can't determine from the CNET story whether it is or not -- it has very few specifics), then the feds are simply ordering Microsoft to live up to the terms of the contract.
I definitely want courts to have the power to make a company (of any size) deliver on the contracts it signs. Otherwise contracts can't be enforced.
Re:I feel bad for Microsoft (Score:4, Insightful)
Questions.... (Score:5, Interesting)
Re:Questions.... (Score:3, Interesting)
But, when you went to fetch the file from Microsoft, their web site contained an abscure reference to rmi, and directed you to their ftp site. I went to the ftp directory, and looked, and looked, and I couldn't find rmi.
Finally, I found the file. Every file in that directory was listed in uppercase, except for rmi.zip, which was lower-case. This made it extrememly easy to overlook when scanning a directory listing.
I have to admit, I kind of enjoyed the cleverness of the whole thing.
I don't like MS, BUT ..... (Score:3, Insightful)
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
Re:I don't like MS, BUT ..... (Score:2, Informative)
Re:I don't like MS, BUT ..... (Score:2)
I have to agree, this ruling is complete and utter bullshit.
Microsoft had an agreement with Sun to ship a Java implementation (AFAIK), and they broke this agreement by shipping an incompatibile implementation.
The worst that should have happened is that Microsoft be forced to pay Sun money in damages and possibly have to update the old JVM via Windows Update or something, to make it compatable with the Sun specs.
I disagree with what Microsoft did, but they should not be forced to include Java in new Windows releases if they choose not to.
Re:I don't like MS, BUT ..... (Score:2)
I'd mod you up funny, but I don't have any mod points, nor can you mod a topic that ou've posted on
Re:I don't like MS, BUT ..... (Score:5, Interesting)
The difference (Score:3, Informative)
They were under contract to keep java in windows... and they broke it.
If they had a contract with macromedia, and then broke it, they could be made to stick to it as well.
Re:The difference (Score:2, Informative)
For those of you more interested in blurbs and sound bites from the article:
Sun, based in Santa Clara, Calif., claims Microsoft views Sun's Java software as a threat because it can run on a variety of operating systems, not just on Microsoft's Windows.
Among tactics cited in the lawsuit, Sun alleges Microsoft promoted an incompatible form of Java that worked best on Windows and, most recently, dropped it from Windows XP, which was introduced in 2001.
Re:I don't like MS, BUT ..... (Score:5, Insightful)
Have people already forgotten that Microsoft has been convicted of the most anti-competitive and anti-free-market behavior possible? That the U.S government has been trying for a decade to rein in their behavior and bring some semblence of competition to the PC market?
Re:I don't like MS, BUT ..... (Score:2)
With java they licensed java from Sun, then broke the rules of the contract. Because of their breaking the rules they have intentionally hurt Sun's product (dilution of trademark idea here), which is why when you start a new "java" project with j++ you get a little message about using MS specific extentions makes it incompatible with other java implimentations. Basically there needs to be a penalty for breaking the contract and the harm done to Sun's java product. To remedy this, the courts (judge here) is saying that they must ship Sun's JRE with windows.
So, while fair competition is an admirable goal, MS is anything but admirable in this case. They broke the contract with Sun, used bad tactics to harm Sun's java environment, and then finally tried to sweep it away and hide the fact of what they have done. Then looking at MS's
And as a counter to BTW above, though I use java everyday (infact we are now in the process of migrating from msjava to java) I have no great love for the language. It has some very nice features, one being the base libraries, I would still prefer coding in C.
Re:I don't like MS, BUT ..... (Score:2, Informative)
PS - I wasn't quite right when I said that "The judge has decided..."; the trail has barely even started, the judge has officially decided nothing. This ruling is because the judge thinks that Sun will probably win, but Microsoft could use delaying tactics to put off an official ruling until irreparable damage to Sun/Java has been done, so until a ruling comes this will make such delaying tactics less successful.
Because... (Score:3, Insightful)
Re:I don't like MS, BUT ..... (Score:3, Interesting)
You say that Sun's Java and Microsofts
The problem is, Microsoft cheats. Microsoft is trying to guarentee their win before Sun even enters the ring. Microsoft has gone to court, and the courts have ruled that Microsoft has illegally used their monopoly to their advantage.
Once Java was created, Microsoft realized that if it took off, many programs would no longer require Windows anymore to run. Microsoft then attempted to hijack Java by creating their own incompatible Java VM. Microsoft was using their monopoly to force this incompatible VM onto consumers. Microsoft was trying to use their monopoly to beat out Sun's Java.
Well, AOL didn't try to ship their own version of MSN, try to pass it off as the real MSN, when in reality it wasn't approved by Microsoft. Microsoft tried to ship their own version of Java, pass it off as Java, when in reality it's not truely Java.
Microsoft only forced their incompatible Java VM long enough until they could get
Sun just wants a fair fight. Microsoft wants to kill them before consumers can pick the winner for themselves. Microsoft's trying to set themselves up as the winner before the fight even starts. The justice system was right in saying that Microsoft cannot use their power to force Sun out of the marketplace.
What Microsoft is trying to do is illegal, unethical, unfair and bad for consumers. It's why using a monopoly unfairly is illegal. The government is supposed to help the people and be run BY the people. Microsoft isn't supposed to make choices for us, and it definately isn't run by the people.
How hard is it? (Score:5, Interesting)
Does anyone have details of what Microsoft claims was so hard about installing Java with Windows? Given that Sun already provide a complete Windows installer [sun.com] why can't they do this in 120 days? How could this "harm large corporate users". I know Microsoft are just stalling, but what argument did they put forward to the judge? Clearly it wasn't that convincing...
Re:How hard is it? (Score:2)
While I completly blame Siebel for writing to a lame Java API (Siebel is known to be very _very_ pro Microsoft), it would harm anyone who has implemented Siebel.
Re:How hard is it? (Score:5, Insightful)
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.
Ok, now where's the CLR (Score:2, Funny)
This spoke volumes... (Score:2, Insightful)
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."
It will only matter if... (Score:3, Insightful)
http://java.sun.com/getjava/index.html
Which version of Java? (Score:3, Interesting)
Is MS shipping Java1.4? 1.1? 1.2? Some truncated version of one of the above?
Too little, too late (Score:3, Interesting)
The web community has overwhelmingly chosen JavaScript for advanced web-based functionality. Java applets are a niche these days, and will most likely remain that way.
Java on the desktop is in sorry shape. You can choose AWT (which is too limited) and Swing (which is too big, slow, and some people think, ugly). It won't be able to compete with the nice native GUIs you get with
I can't think of very many developers who think writing their desktop applications in Java is a good idea. And I can't think of very many JavaScript developers who will switch to Java once Microsoft bundles Java with Windows.
Besides, we're talking about Microsoft. Who here DOESN'T think Microsoft won't taint Java in some way? Raise your hands. I've got a bridge to sell you.
-Teckla
Re:Too little, too late (Score:3, Insightful)
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.
Re:Too little, too late (Score:3, Informative)
AWT is basically deprecated (as the primary GUI system, parts of it are integrated into Swing), and Swing is not 'ugly.' The native look and feel is a bit distateful to a lot of people, but all of my Swing applications look suspiciously like the platform that they run on... So if the default MS Windows look is 'ugly', then yes Swing on Windows is ugly. If the default Aqua look is 'ugly', the same applies.
You seem to be caught in a circa '97 approach to Java on the network. Applets are not about animating icons or handling the form work that Javascript does well. They are about delivering complex programs that do complex things above and beyond what Javascript can do. In many ways they are very complimentary technologies. There is a definite place for Java on the web (and on the Desktop for that matter)... For example, we've managed to support many platforms by our choice of going with a Swing Java desktop application as support for our Palm apps... With minimal effort.
Re:Too little, too late (Score:3, Insightful)
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 [slashdot.org] 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.
Do your Homework (Score:5, Informative)
We can only hope ... (Score:2)
I used to be a big Java fan, but it's become so bloated, and there are so many better alternatives out there, that I'm no longer as interested in its fate as I used to be. Almost anything you want to do with Java, you can now do faster and more efficiently in some other language. Once Parrot is up and running, the OSS world will finally have a full-fledged VM that can beat the hell out of both Java and anything Microsoft is likely to come up with. Web services are already falling to PHP, Python, and mod_perl. The efforts of Zend (PHP) and the Parrot (Perl and Python) team will accelerate this trend. And depending on how well Parrot can be integrated into native API's, we may well be seeing real "write once, run anywhere" apps written in Python or Perl within a couple of years. It's funny to think that something that started as an April Fool's joke may be the actual Next Big Thing.
In other news (Score:2, Funny)
If the court can force Java... (Score:2)
We shall see...we shall see...
Vegas odds? (Score:2)
But whose Java VM will Microsoft use? (Score:2)
Which Java VM will Microsoft use? Will it be Sun's current 1.4.1 (which works best in Windows 2000 and XP)? Or will it be one that is supposed Sun-compatible from the likes of HP, IBM, and so on?
PLease don't start making applets again (Score:2, Informative)
The web is actually a lot better now developpers know that ActiveX, Java and full Flash sites have a lot of problems attached. Finally there is some knownledge about (and government pressure for use of) the W3.org principles. Portability and accessibility are beginning to become standards for the web. Furthermore, if you really need more action in your site, Javascript can do a lot.
Everyone, whatever disabilities or browser they have, should have the right to use the web. (and Java is still not standard in say Lynx, and electronica for blind people will fail seeing the information).
Java server side is fine, Java for applications is ok, if the application is fast enough or people are willing to wait for it, please please never make applets again...
So actually if everyone listens to me
Yeah, well (Score:2)
Wow... (Score:2)
Of course, anyone with half a brain realizes that if Java hadn't been torpedoed by Microsoft the monopolist early on it would be the premier method for delivering interactive web content like forms and 98% of the other things Flash (truly a crappy alternative IMO) is used for now.
So, WOOHOO for Java winning a round or two - its a nice trend that I hope helps it pick up big momentum. Java is quickly becoming the best choice for most modern, industrial strength software development. :-)
Must ship in 120 days with Java? In what form? (Score:2)
1. MSFT still haven't shipped after that deadline, what will *really* happen.
2. Its so broken people will hate Java and then MS comes back to court and states that it had to remove Java as it did not jive with its components, so was removed in the best interests of the company.
StarTux
In what ways did it not meet standards? (Score:3, Interesting)
Re:In what ways did it not meet standards? (Score:5, Insightful)
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.
This is a load of smelly poop... isn't it? (Score:4, Insightful)
That's sort of obnoxious, like having a little brother with ADD and a mean streak.
As a developer (Score:3, Insightful)
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
What about product updates? (Score:4, Interesting)
Yes, XP SP1 (Score:3, Interesting)
The Bigger Microsoft News Today (Score:4, Informative)
"Microsoft sets dividend, stock split"
Microsoft is the last of the Dow 30 to start paying a dividend, and paves the way for other tech companies that have held out paying dividends. Should be an interesting morning in trading for MSFT [yahoo.com].
What was Sun thinking? (Score:5, Insightful)
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.
Get a clue! (Score:3, Insightful)
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.
Law is just dumb? (Score:2)
It's very simple. Microsoft broke the law. Specifically, Microsoft broke the law in an attempt to keep Java off of Windows. Obviously, if MS viewed Java as such a threat that they felt they had to break the law to stop it, then it seems rather appropriate that the law now be used to make MS carry Java and rectify the damage that their activities caused.
Or maybe that's just too difficult to follow.
Re:thats just dumb (Score:5, Informative)
Re:how about the reverse (Score:3, Insightful)
You know what, you're absolutely right.
is exactly the same as Thank you for clearing that up.Re:About damn time (Score:2, Interesting)
Re:About damn time (Score:4, Insightful)
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.
Re:consider this... (Score:2)
You fools never think about the reversed situations.
AOL isn't a monopoly. GM isn't a monopoly. Sony isn't a monopoly. Apple isn't a monopoly. Linux isn't a monopoly.
If Linux WAS a monopoly (which, btw, makes no sense at all, given that Linux doesn't represent a single entity as does MS), we would probably all hate it too, and rally behind one of the underdogs. Perhaps at that point we wouldn't mind the .NET framework so much. Did you ever consider that?