Linked by Thom Holwerda on Tue 23rd Jan 2007 18:58 UTC, submitted by anonymous
Java IBM has released an SDK for Java 6. Product binaries are available for Linux on x86 and 64-bit AMD, and AIX for PPC for 32- and 64-bits. In addition to supporting the Java SE 6 Platform specification, the new SDK also focuses on, Data sharing between Java Virtual Machines, Enhanced diagnostics information, Operating system stack backtraces, Updated jdmpview tool, platform stability, and performance.
Thread beginning with comment 205085
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Not bad
by croco on Tue 23rd Jan 2007 22:06 UTC in reply to "Not bad"
croco
Member since:
2005-09-16

Very interesting. I can remember as we developed some "heavy" (about 15 mio. code lines) distributed enterprise applications with 1.3 (or was it 1.4?) it was pretty impressive how better on the server side JDK from IBM was. It was much more stable, less buggier, code much cleaner and able to use 4GB of RAM on AIX. Not sure about speed performance. I think Sun was better on that one. However it was never a problem for big companies, where new/more hardware is the answer.

Reply Parent Score: 1

RE[2]: Not bad
by ormandj on Wed 24th Jan 2007 01:13 in reply to "RE: Not bad"
ormandj Member since:
2005-10-09

Having dealt with IBM on the same front/scale of project, I think the key part of your statement is "AIX". There is no Sun JVM on AIX (or at least - there wasn't back when I was working with it in '03). How can you compare the stability/bugginess/code cleanliness/etc of a non-existant package with an existing package?

Not getting into specifics, but I've dealt with IBM's older (Websphere/HATS/etc) stacks and their more recent stuff, and I've had a lot of "strange" things take place. Almost as a counter-point to your post, I've found Sun's Java much more stable assuming I stuck within the constraints of the provided libraries. Slapping in all kinds of third party frameworks into the mix can complicate things a bit. :p

That said, you won't see me running this SDK anytime soon!

Edited 2007-01-24 01:14

Reply Parent Score: 1

RE[3]: Not bad
by croco on Wed 24th Jan 2007 01:51 in reply to "RE[2]: Not bad"
croco Member since:
2005-09-16

> ...I think the key part of your statement is "AIX"...

No, it's not. It was only one part of the software running on AIX. As I said, it was one pretty much distributed (mostly with CORBA) piece of software.

> ...How can you compare the stability/bugginess/code cleanliness/etc of a non-existant package with an existing package?...

IBM JDK was used not only on AIX.

> Not getting into specifics, but I've dealt with IBM's older (Websphere/HATS/etc) stacks and their more recent stuff, and I've had a lot of "strange" things take place.

Sure. I'm also not a big fan of WebSphere. Too bloated, too slow, too buggy. IBM VisualAge for Java was much better. For me JDK integration and Debugging in VA was much better than even in eclipse now. And WebSphere is actually not so old. ;-)

> I've found Sun's Java much more stable assuming I stuck within the constraints of the provided libraries.

This is really the first time I hear somehing like that from somebody.

Reply Parent Score: 4