Post a Comment
Different OS support (s390 and AIX, for example), and in some cases, better performance. Also a slightly different license, although I can't explain what the impact is. For the most part, given platforms they both support, I have found Sun's Java and IBM's Java to be 100% swappable.
there are a number of projects that use sun-specific classes and require sun's JVM. OpenNMS is one of them, and I believe parts of OpenOffice 2.0 still. While using these classes are a bad idea from a portability standpoint, it appears that it happens often enough to be annoying (like when I tried compiling opennms with a non-sun jdk).
I think the work on decruftiying OOo2 has largely been done, since it works fine for me using gcj, which certainly does not ship the unspecified sun.* classes at all.
Check out the Classpath Wiki at http://developer.classpath.org/mediation/ClasspathMigration for tips how to improve portablity and quality of Java code.
cheers,
dalibor topic
If you download the JavaDocs for your SDK Sun explicitly says not to use those files.
http://java.sun.com/products/jdk/faq/faq-sun-packages.html
This is linked from the main JavaDoc page: http://java.sun.com/j2se/1.5.0/docs/index.html
I read those when I was first learning programming back in grade 10 ... so if real developers haven't bothered to read those then it can't say anything good about their product.
Frankly anything that uses sun.* packages is like it was using proprietary extensions... even worse than SWT .
This is not a release; this is still in beta. IBM Java2 5.0 beta JREs and JDKs have been available for weeks. See http://www-128.ibm.com/developerworks/java/jdk/ for details and to check status of IBM's Java2 5.0 work.
There is also a BEA version of Java 2 SE 5.0 (BEA JRockit 5.0) for some time now. See: http://www.bea.com/framework.jsp?CNT=index.htm&FP=/content/products...
Hire Alan Kay and his team. Embrace and extend Smalltalk. Re-introduce it as a major enterprise development system alternative via eclipse that IBM has fully commited to.
There needs to be another major player in the enterprise development market to counter J2EE and .NET
SmallTalk is perfect and already has a close cousin/scripting platform in Ruby.
SmallTalk and Ruby make a very powerful one-two-punch to the J2EE and .NET hegemony.
Smalltalk a "flimsy language"? Are you kidding? Have you ever coded in VisualAge Smalltalk Enterprise? I somehow doubt it. How about Cincom's Smalltalks?
Smalltalk is used by many of the world's major corporate banks and financial institutions, as it has a proven track record of stability and power, coupled with arguably the easiest/most elegant OO implementation possible.
You can run headerless Smalltalk on some pretty heavy-duty back-ends (AS/400's and mainframes say), and it's been in use for decades.
THe original post was OT yes. Your answer was however poorly researched.
I know nothing about Ruby, so I will not comment on it.
Well, if Apple has any brains other than to put out pretty boxes, they will bump up Objective-C, which is an incredible powerful, yet simple platform.
It is extremely sad they haven't done anything major with Objective-C lately. Yes, OS X has Objective-C code in it, but there's a lot more they could be doing with it. They definitely need to promote this great platform, which they practically own.
What do you mean by Apple practically owns the platform.
Apple bought the rights to Stepstone's Objective-C compiler by merging with NeXT.
Apple's operating system will shed a buttload of Carbon, if not all of it coming in Leopard.
Whether they return to the Enterprise like NeXT did is one of the reasons I didn't want to wait around.
IBM java has proved a lot more convenient for me in certain circumstances. A multithreaded multimedia app I wrote using the java Qt/KDE bindings crashes terribly with Sun's JRE (with error messages I can't find with google at all). Runs just fine with IBM's JRE.
Of course I am willing to believe it could be something with my program or how it uses Qt (the SWT and Swing alternate frontends work just fine), or something with the Qt bindings themselves. All I'm saying is in that particular case IBM's works, Sun's doesn't.
Anyone know why if you try to run 2 different java apps simultaneously, 2 instances of Suns jvm start running? Does the IBM version allow one instance of JVM and run multiple apps on it?
Afaik, no one has done an mvm (multi-vm) yet although there is talk of one coming from sun in the distant future. Of course that'd be nice from a memory usage and start up time perspective, but there are problems with the idea.
One is that monitoring becomes trickier. Right now, things are already so abstracted from the operating system. All the os knows about it is that there is a java(.exe) process running and nothing more. That's tough from a user perspective because two completely different programs have the same name and from an os perspective because you can't use facilities like services without some hacking.
The more push there is towards a mvm like this, the more the virtual machine ends up reimplementing things that operating systems have been doing well for years, like memory/process/thread management. Eventually I figure the mvm will become so comprehensive that we'll just rip the os out from underneath it and run the vm directly on the hardware.
Wrong. The new JVM is based on J9, which contains no Sun IP. http://www.cs.ualberta.ca/%7Eamaral/IBM-Stoodley-talks/UofAKASW...
Since IBM is so big on open source, why don't they release their JVM under the GPL/LGPL or similar and stop all the arguments about how free java is?
Because there is no services revenue to be gained out of doing this. They get to bash Sun for not doing it, but don't do it themselves. IBM are no friends of the opensource movement, they support Linux because it allows them to put consultants into your company. If they really supported opensource they would opensource OS/2, AIX, all the rational tools and clearcase.
Unfortunately the slashdot idiots have bought the idea that ibm are their friends.
It's about time! Back when Java 5 was new, I would use IBM's JVM on my workstations rather than Sun's. I've always found it to be faster and easier to work with (outside of where they're standard, of course). Then Java 5 started gaining popularity and I, as a software developer, thought it well to adopt the newest changes to the language as early as I could since it was inevitable that they would be used. Alas, IBM's Java 5 JVM was taking a while to come. Thank goodness it's in Beta.
I'm developping a service container using Java 5 api (ThreadPool, ReentrantLock ...) and I noticed differences between Sun's and IBM's SDKs.
The behaviors are different, I've got poor performances with IBM's SDK whereas everything is good with SUN's one.
The response time to a service request is 5sec with IBM and 30msec with SUN. There may be some troubles with ThreadPool. I'm investigating the problem, but if it is a problem of threadPool it's not very good for IBM.



