Oracle: SELECT * FROM Sun

Posted Apr 20, 2009 22:10 UTC (Mon) by Cyberax (✭ supporter ✭, #52523)
Parent article: Oracle: SELECT * FROM Sun

I hope that Oracle at last starts real JVM development. It's been stagnated for a looooooong time now. Java7 won't have a lot of expected features, and it is not even close to release! It's like a Windows Vista of Java world now.

Oracle: SELECT * FROM Sun

Posted Apr 21, 2009 0:22 UTC (Tue) by lakeland (guest, #1157) [Link]

Java is Oracle's preferred method of implementing stored procedures. The database has its own JVM which (in my opinion) had been stagnating and falling behind LINQ + .NET. An injection of effort into this could be interesting, turning Java into a first class database language.

Oracle: SELECT * FROM Sun

Posted Apr 22, 2009 2:50 UTC (Wed) by gnu_andrew (guest, #49515) [Link] (1 responses)

Hardly. Development on HotSpot is very active, is now finally out in the open and I believe the changes in the OpenJDK7 HotSpot tree have made their way back into the proprietary Sun Update releases for JDK6. If anything, things have improved.

As to the delay with *Java* 1.7 (as opposed to Sun's implementation, the JDK) this has been delayed by the mess that is the JCP and the deadlock between Apache and Sun over Harmony and TCK licensing. We can only hope Oracle can improve on this situation; there is certainly plenty of scope!

Oracle: SELECT * FROM Sun

Posted Apr 22, 2009 4:12 UTC (Wed) by foom (subscriber, #14868) [Link]

> deadlock between Apache and Sun over Harmony and TCK licensing

I still find it quite amusing that Apache's new Java implementation effort was named "Harmony".
They claimed the purpose of the project was to bring all existing efforts together, and yet chose
a license which disallowed cooperation with any of the existing (long underway!) free Java
implementation efforts...and thus ended up starting a new Java implementation from scratch.

Every time I see the project mentioned, I chuckle at the sheer gall of it. It was quite a masterful
fake-out: they even had the Classpath developers tricked into thinking they actually wanted
cooperation, for a while.

And given such, I'm really not surprised that Apache is causing a deadlock in JCP...seems pretty
much par for the course. "Yes, we really want to cooperate with you. Really. Just do everything
exactly on our terms, it will be great!"

Sigh.