Blackdown Releases a 1.4.1 JDK
gholmer writes "The Blackdown project has finally released a production version of Java 1.4.1 for both ix86 and Sparc on Linux. This much-awaited release gives Linux users another choice for Java besides Sun's and IBM's."
What about using the Java front-end for the Gnu Compiler Collection?
(I'm not a Java developer, but I was under the impression that it, also, was another choice besides Sun's and IBM's.)
I'm curious, why would I want to use Blackdown or IBM's Java over Sun's Java? Am I missing some wonderous features or something?
Any tables out there comparing the various Java Flavors?
Seems to me that Sun's Java is the most mature of the Java's, and that Sun engineers have the most experience with Java and therefore will probably create the best Java implementation.
Am I wrong?
"Can of worms? The can is open... the worms are everywhere."
Jvaa WebStart rocks! apt-get, emerge, windows installer, bsd ports all pale in comparison to WS. You just go the web page of the app click a link and the program downloads and installs itself. The downloaded app doesn't have full access to your system resources (printer, network, loacl disks etc.) until you give it permission. So you can download random safe self-contained applications without worring about malicious authors. Each time you run the program it will (if the networks available) check the server for new versions, and automatically upgrade. Its so quick & painless. Where i work we have a intranet app thats rolled out to 600 people and since we started using websart what was a real admin head-ache is now something that just happens. The app is maintained by us and upgrades could only be once a month, because we had to guarantee everyone used the same version - not as easy as you think in practice, but webstart is my favourite thing ever!!!
finally with the blackdown release the webstart icons will be integrated into the gnome desktop so the java app will launch just like a native app (is done this in windows for ages) our linux users will be so happy!!!!
i'm so pleased about this i just pissed my pants
Now we can finally build mozilla with 3.2 and drop all this crazy crap we've been doing to work around it. I can't believe Sun hasn't put out a 3.2 compiled version yet (plans for 1.4.2 to be though). I don't know about IBM. Anyone?
"There's so much left to know/ and I'm on the road to find out." -Cat Stevens
So J++ programs have the ability to create run-time errors in programs written in Sun's Java. Or does the sabotage occur during the compilation phase? Or was Sun's bait-and-switch WORA business plan the thing that got sabotaged?
Actually MS designed its J++ product so that Java developers targeting Windows could develop their application faster and deliver better performance.
Those developers who wanted a cross-platform solution would probably just use Sun's free kit rather than buying J++. In fact it's rather likely that most developers who think cross-platform applications are important are Unix users and couldn't use J++ anyway.
I sure would like to se some detailed changlog on the blackdown work. Its based on the sources from Sun, now what the heck is diffrent ?
"J++ was never the problem."
Tell it to Sun and the Courts. The antitrust ruling against MS was based on the theory (that I don't subscribe to) that developers would develop a Java application on Windows using MS's extentions and be suddenly suprised it wasn't cross-platform. It wasn't about standard Java breaking on Windows.
If there are incompatibilities at the JVM level, it's probably because Sun wouldn't allow MS to update the JVM due to their dispute about J++. Now, of course, MS doesn't want to include Java at all which also pisses off Sun.
A project I am working on involves using soap (ApachesSOAP) as a transport layer and performing serialization of data to xml using Castors xml abilities (so xerces as well). It also uses the JDO part of castor to persist the data, and also to keep logs and some more complex things as well (PostgreSQL for this test). (I am running system on a Linux 2.4.19 machine with a 2.20GHz Intel CPU. (No swapping occured)
Here are some numbers for a test involving simply serializing one of the complete object trees of data using castor, in a loop executed 1000 times:
Sun JDK 'java version "1.3.1": (avg/3) 5.8s
Sun JDK 'java version "1.4.1_01"': (avg/3) 6.4s
Blackdown 'java version "1.4.1": (avg/3) 5.3s
Sending a message with the the above generated xml full cycle through the system (multiple threads of execution here, multiple database connections as well (pooled), passing data over soap, etc), looped 200 times took the following times: (again, avg.)
(sun 1.4.1): 44.2s
(sun 1.4.1): 44.6s
(bd 1.4.1): 41.4s
In both the coded test, and the real world situation, Blackdown's JDK outperformed Sun 1.4 and 1.3 jdks.
"It wasn't about standard Java breaking on Windows."
You're off a little bit. It was about standard Java breaking on Windows, namely JDK 1.1. When Sun released JDK 1.1, the first non-toy version of Java, Microsoft decided that they would take bits and pieces of new JDK, but substitute their own incompatible pieces for the rest. The trademark fight, the first legal battle between Microsoft and Sun on the matter, was whether Microsoft could still call the result Java. The court said they couldn't. And so they called it J++.
For example, Microsoft refused to use JNI, using their own RNI instead. Of course, they claimed RNI was easier to use, and perhaps in some ways it was. However, it meant that if you wanted to integrate native code and support the Microsoft VM, you either had to do dual development, or code to MSVM only.
Interestingly, Apple has had their own native interface too, called JDirect, which was even easier than RNI. But they fully suppored JNI as well, and you could mix the two. (The interface has changed since then, but there are still dual-supported interfaces.)
Why didn't Microsoft take this approach if they really thought they could do better? That's the crux of the matter. Sun and others would argue that Microsoft was trying to break cross-platform Java. I would argue they have a point.
From my experiences with IBM's and Sun's 1.3.x series, IBM tends to be much faster but also consumes more RAM.