Alexander Schunk's Blog

Java 7 GA 09 too late?

Java 7 09 GA?

A short glance at SUNS official "Production Cycle" paper reveals that Java 7 will be published some time in 2009 which is two years ahead.

Since Microsoft has released .NET 3.0 and fit C# with lots of new features i think publish date of 09 will be a bit late for Java 7.

The list of features and core/extension APIs currently discussed looks - i.g Concurrency API, JavaFX, JScience, etc. - great but may not worth the effort when Microsoft is far ahead.

The reason for not publishing Java 7 before 09 are - according to SUN - problems with porting Java to Solaris.

However Users of other plattforms may not wait that long so may be bulds of Windows/Linux plattforms may be available a bit earlier.

Since the dates mentioned in the paper are only "guesses" the actual official release date might be earlier - hopefully not later.

Comments

• I need to develop a php live chat application for my website Call center services to have a better first-time interation with my visitors. I have an option to choose a .NET framework or a java foundation. Researched for a few days on forums and blogs as to a more stable option. Still havent been able to decide. Currently I'm using an application of an outside vendor on my website. I want to have it made in-house and market it too along with my business. Can you suggest the better option. Also, I was contemplating AJAX ? Would that make sense?

  Posted by: peter_forrester on July 07, 2007 at 07:32 AM

• Hm... in this case i think its a matter of personal favour and experience with the framework.

  Also this depends on your local tier setting and evironment.

  You can build a simple chat with Java networking API and publish this as an Applet if thats what you want to.

  Posted by: alexanderschunk on July 07, 2007 at 07:41 AM

• At first, I don't think 2009 is too late. However, I would like to see a separation of the language and Runtime from the Framework (maybe modules will allow that). The reason is that it takes far more time to get new language features right than API - an API lifecycle may be long until it gets depricated, but language changes are forever. So why wait for the the concurreny API when it's almost done and doesn't require a language extension. Also one could have a binding framework now, and if it evaluated, we know whether there's a for property language changes ;-)

  Posted by: zero on July 07, 2007 at 08:44 AM

• I think that JavaFX will be a part of "Consumer JRE" slated to be released early 2008.

  Posted by: kirillcool on July 08, 2007 at 03:46 PM

This work is licensed under a Creative Commons License.