Comments on: Hey Gosling: This is why we don’t use Java 5.0 yet!

By: Jerry

Jerry — Tue, 23 May 2006 23:45:08 +0000

weblogic 8.1 is not compatible with jdk 1.5. I use jdk1.42 and getting String builder related error when ” ” are used for strings. Kindly Help

By: Infernoz

Infernoz — Thu, 09 Feb 2006 13:36:06 +0000

I use a personally backported version of StringBuilder and other classes for java 1.3/1.4 in my work code (in a non java packages), because I must support legacy java, but still need flexibility/speed; Sun made plenty of dumb mistakes in the past *, so should expect this! It is not hard to backport basic classes like this (without 1.5 extras) if you have the 1.5 JDK (with src.jar), try it. I doubt I will release this openly given license concerns.

IMHO A synchronized string buffer is a really dumb idea, I doubt that it is genuinely useful or safe in a multi-threaded environment, given that text sequencing could cause some nasty bugs and there are more efficient/safer ways to handle thread safety, e.g. synchronizing on the buffer object!

I also have major gripes about classes having private rather than protected values, so making subclassing a pain (e.g. java.util.* and java.io.*), but is with little if any security benefit, so yet more class source code copying has to be done!

By: Brandon Werner

Brandon Werner — Sat, 07 Jan 2006 04:24:28 +0000

That is a damn good point Dmitry, Apple’s insistance on only providing Java 5 to upgraded OSes only smacks Sun & the idea of Java in the face.. hard. Java is platform independent, but Apple is the only entity that controls it’s Java distro (because of PowerPC compilation I’m sure) and uses it as leverage.

I’m certain when Apple moves to the Intel platform Sun will have a UNIX build of Java5 for Mac no matter what OS is running. Since Apple is abandoning Cooca Java binding going forward, there is no reason for deeply customized Apple distros or .jars anymore.

By: Dmitry

Dmitry — Sat, 07 Jan 2006 02:01:34 +0000

The real reason “why not 1.5…” for our product is that it must run on the Mac OS X, but not necessarily on Tiger.
1.5 supported on Tiger only and nobody knows when all the Mac owners will migrate to Tiger (the migration is not free)

By: Vinny Carpenter’s Link blog » links for 2005-12-21

Vinny Carpenter’s Link blog » links for 2005-12-21 — Thu, 22 Dec 2005 15:21:20 +0000

[...] Brandon Werner � Blog Archive � Hey Gosling: This is why we don�t use Java 5.0 yet! Whenever there is a major JDK update everyone on the Sun Microsystems side seems to love to beat the drum of upgrading. This leaves developers in a situation where they love the new features of the new JDK but quickly find out the rest of the world isn� (tags: java5.0 java) [...]

By: Klaus

Klaus — Thu, 22 Dec 2005 12:19:31 +0000

Hi Mark,
I have looked for such wonderful Eclipse settings, that allow for 1.5 source code with generics, enums, annotations, java.util.concurrent.*, etc. and really give us the 1.4 bytecode at the end. I don’t think that this is possible.
If you use “Compiler compliance level “5.0″ you CANNOT set the “Generated .class files compatibility” to “1.4″! Otherwise the Eclipse people would have to provide a COMPLETE Java 5 to 1.4 backport…
My current solution right now is to use the new OS project Retrotranslator if we need one source for both 1.5 and 1.4.

By: Trinity

Trinity — Thu, 22 Dec 2005 06:20:08 +0000

We migrated from 1.4.2 to jdk1.5 successfully. jboss4.0.3 has ejb3.0 support.

By: Jason

Jason — Wed, 21 Dec 2005 19:10:15 +0000

“the platform of choice of Java developers, Apple Mac OSX”

Really??? I’m not saying it sucks - I really don’t know anything about it. But that’s because I don’t know ANYBODY developing on it. Am I living in a bubble?

By: Mark

Mark — Wed, 21 Dec 2005 15:43:59 +0000

Eclipse has settings to parse Java 5 source-code but emit Java 1.4 classes. But I must admit I haven’t tried it out yet.

By: Vinny Carpenter’s blog » Daily Del.icio.us for Dec 20, 2005

Vinny Carpenter’s blog » Daily Del.icio.us for Dec 20, 2005 — Wed, 21 Dec 2005 04:37:50 +0000

[...] Brandon Werner Â» Blog Archive Â» Hey Gosling: This is why we don’t use Java 5.0 yet! » Whenever there is a major JDK update everyone on the Sun Microsystems side seems to love to beat the drum of upgrading. This leaves developers in a situation where they love the new features of the new JDK but quickly find out the rest of the world isn’t [...]