Tuesday, June 20, 2006

The Java big ball of mud rolls on...

The dudes working on Mustang now tell us they have incorporated their own specially packaged version of Apache Derby into the Java 6 SDK. I don't know why Sun keep adding all sorts of junk into Java that just doesn't need to be there - the classic big ball of mud anti-pattern.

What would be more useful is to trim down the JDK/JRE to a small core package, then provide a dynamic mechanism that downloads libraries when needed. (Maven does a nice job of handling this at compile time.) At a minimum this would allow Java to compete on a more equal footing with Flash on the web tier; nobody wants to wait 30 mins to download and install Java just to see a simple animation.

3 comments:

David Van Couvering said...

Just to clarify, Java DB is going into the JDK, not the JRE. Web apps that want to use Java will not be impacted by this, as they generally only use the JRE; this shouldn't affect download time.

Xin Zhao said...

I feel the client DB is definitely a good thing. But still could not find a good pattern to use it.

Robert Maldon said...

True this is going to be added to the JDK, not the JRE, but I still think it is an unnecessary bloat. What is wrong with just downloading Derby or hsqldb from their respective websites? (In this case it is even worse since Sun will probably fork Derby to create "Java DB".)