Derby controversy

Posted by    |      

Usually I don't like to climb into these kind of discussions - I usually keep quiet unless I have something more to add than metoo. But forgive me for mentioning that, on balance, I agree with the many people arguing that bundling Derby in the JDK is a Bad Idea. My concern is that this decision naturally forces projects like Hibernate to have to support Derby, no matter what our better judgement as to the maturity/stability of the product at this stage. Perhaps if/when Derby has shown itself to be a truly production-ready platform, this decision could be better justified. But for now, Derby is neither usable in production, nor is it really a good choice for development (HSQL is much more usable at development time, and that is what 95% of people are using).

It would be really nice if Sun would reconsider this decision. Perhaps the solution is simply to offer two different download bundles, one with Derby, one without, and Let The People Decide :-)

UPDATE: I'm also amazed that Sun would want to risk sticking the word Java on this product. Like the Java Desktop, it seriously risks devaluing the brand.

Back to top