Defecating on a JDK

http://jroller.com/page/fate?entry=defecating_on_a_jdk

In a rather perplexing move, it's announced that the Java 6 JDK will include Derby, the turdy little unwanted IBM poop plopped onto Apache (about par for the course, since large swathes of Apache seem to exit solely as an IBM marketing tool.)

What's perplexing about this decision is how incredibly arbitrary it seems. I have yet to see a single rational justification of its inclusion, even from within Sun or from the community at large.

It's one thing to suffer from the tyranny of the masses. We have plenty of cases of that in Javaland, do we really need to now add arbitrary bizarre decisions that not only pop up out of nowhere, but also have nothing at all do with the community?

Honestly, not even the JDK6 Expert Group decided on this addition. It's literally as if someone at Sun woke up one day and thought 'you know, I miss the old days when we could add random shit to the jdk without all this community and expert group nonsense, I'm going to sexually arouse myself now by doing just that', in one of the most harmful public displays of nostalgia ever seen in a technical forum.

I honestly cannot conceive of a single reason for this. It doesn't even make life easier for anyone. You can't rely on it being there since it's not in the JRE, you can't actually do anything with it since you have to ram various awkwardly shaped objects into unexpected orifices to create a db and manage it using derby's amateurish and unpleasant tools. It'll work out of the box much the same way as an Oracle 8 install CD can be considered functional.

Even the silly 'explanation' from Mark Reinhold on JavaLobby says nothing compelling. It really does seem like a completely random decision based on a freakish whim. The motive in fact is fairly evil, getting people hooked onto JDBC 4, which will be a nasty thing to hook people onto since invariably they'll need to move onto a real database, and end up being exactly where they are now; at the mercy of the real DB vendors, with nothing useful at all gained from the fact that they got to play with some half baked alpha pile of IBM dingleberries; a dubious joy at best.

This is even bad news for the handful of morons who are incompetent and desperate enough to use Derby. Now you'll have to bend over and invite over a large group of chocolate log miners and perform things your mother would be very upset about just to upgrade your db. Of course, you WILL want to upgrade it. It has hundreds of open issues, and is clearly labeled alpha.

Even if those issues are miraculously addresses in the next few months, we'd still end up with more IBM shit in the JDK. Honestly, when will people finally realise that IBM has never produced anything of worth, beyond genius marketers? How many times must I mention java.util.Calendar and java.text before people start listening?

How hard is it really to install lightweight pure Java DB? We have mckoi, we have hsqldb (in its various incarnations), and we even have a halfassed one from Apache (Derby). All of these (except derby, funnily enough) are very easy to download and install, and are perfectly adequate for testing and playing with and the odd bout of sexual experimentation for the curious. In ALL cases, this should NOT be in the JDK. Why should one DB be blessed above all others? Did we learn nothing from the crimson fiasco? Mark also naively claims 'Vendors of little DBs are already threatened by Derby whether or not a copy of it is co-bundled with the JDK. I don?t see how doing that fundamentally changes the picture for them.' A clearly ludicrous claim; just look at how successful Tomcat is. That lovely servlet engine that'd have gone nowhere had it not been the RI. I don't envy the little guys having to compete against a product called 'JavaDB'.

The branding of the whole thing is equally ludicrous. JavaDB? What next, renaming Glassfish to The Java Application Server and making obscene lawyery gestures at anyone wanting to refer to their appserver by that name?

I'm one of the few people I know who will publicly admit that he's a Sun fan. I think they're an excellent steward of Java, and have done a remarkable job in every way (except marketing of course, I can't think of a company that's more incompetent in terms of how they present themselves to the public or of the ludicrous stuff they seem to push). How out of touch do you have to be to be 'honestly surprised at the reaction to all this' according to Mark? Have you people lost all respect for what we love and care about our platform, and felt that for the sake of consistency, you should whore the rest of the JDK and sell all your products NetBeans style? Come on, surely there are enough technically minded people still at Sun, who have some say and can prevent this travesty from taking place?