• WS* is already legacy.
• WS* will be more and more replaced with RESTful services
• RIAs are overrated, user like simple interfaces (I totally agree on this)
• JavaScript/AJAX are the new old stars of the web, especially with the new browser coming out
• MultiCore isn’t much of an issue (yet) for Web Development
• HTTP doesn’t need an overhaul
• He isn’t sure in which direction Cloud Computing is going.

The 30-minutes interview is available on InfoQ.

Related posts:

1. Netbeans TV Interview with JavaFX Developer Josh Marinacci
2. Javaworld about Applets and Java’s RIA future

• Tool support has still a long way to go, but it is getting better (I really like to see this project to succeed)
• The new Applet plugin is living up to its promises.
• I am more and more impressed by the performance of the Java platform, this will also translates to JavaFX’s performance. A real performance comparison between JavaFX, ActionScript, and Silverlight..
• JavaFX.com will be updated! At last the ugly, ajaxy, and buggy page goes away. Hopefully, the next one will be better and shows JavaFX’s capabilities.
• It seems that the Java team is not affected by Sun’s announced staff cuts.
• Release 1.0 contains a JavaFX Mobile prelease.
• The best at last: JavaFX will support Windows and Mac OSX! Linux support is on its way. This is really crucial, JavaFX can only succeed when it supports all major platforms equally.

Still, there are some open issues:

• I am still not convinced about JavaFX script and about the new language. Maybe we will see something similar to JavaFx what now happens to Java – maybe it will become a multiple language platform.
• The community has to accept JavaFX. Company support would also help.
• Development must be faster. Especially at the beginning (JavaFX has a lot to catch up) short release cycles are desireable.
• Sun must implement a clear vision. It seems that they have intern doubts about what to do.

If you live in the San Francisco area, there is a JavaFX release party. Infos are on JavaFX.com. Btw. Java 6 update 11 was release today.

Related posts:

1. Google App Engine supports Java
2. JavaFX 1.2 leaked before JavaOne
3. JavaOne 08 will be about JavaFX

• Enhanced Java deployment: Deployment Toolkit, Java Kernel online installer, Java auto-updater, and server side requirements are removed.
• Improved performance: Java Quick Starter and Hardware acceleration support
• Improved Look&Feel: Nimbus
• Next generation plugin-in: Applets are back and rock

I haven’t checked all of them yet, instead I concentrated on the things I am really interested: Rich Internet Applications (RIA). Adobe’s AIR and Microsoft’s Silverlight are without a doubt the major players in this field. However, Sun presented at last year’s JavaOne JavaFX and announced that Java’s VM will get an overhaul, so it can compete with the other technologies in the client area. I am still not 100% convinced about JavaFX (maybe the mobile aspect is the key), but I do like the idea that Java is used more on the client side.

Like I started Java programming, I always read Java performance; hence, Java sucks. Ok, the statement was true before Java 5, but since Java 5, especially since Java 6, performance is not an issue anymore. Except the startup of the VM and graphics. Both problems are addressed and should be solved by now. First, I checked the startup and the results is really good. Small Java programs are starting much much faster with the Java Quick Starter (JQS). Before you think, “Ok, another startup process that slows down my machine”, have a look at the following screenshot. The process takes less than 1MB and CPU usage is low as well.

What is the magic behind JQS? The explanation from Test Guidelines for JQS:

When JQS is fully enabled, there will be a new Windows Service running called “Java Quick Starter”. In TaskManager, the new JQS service is running as “jqs.exe”. JQS improves initial startup time for applets and applications by reducing the disk I/O required. This is achieved by periodically prefetching some of the most heavily used Java Runtime Environment files into memory (occupying no more than 20Mb of RAM). Later, when Java is launched, much less disk I/O is required which makes startup much snappier and noticeably faster.

It is all about reducing I/O! The downside of the JQS is that it is Windows only, but my hopes that the Open JDK project will take of a Linux/Mac JQS are high.

The next improvement is about graphics. First, Java now uses under Windows the DirectX 9 API and, secondly, a new Swing theme called Nimbus is available. I couldn’t test the hardware acceleration, but I had a look at Nimbus. Actually, I am following the development of Nimbus for month. My feelings towards the project are kinda torn. It is a must that Java gets a new and more modern standard Swing theme (look at the AIR default theme) because I think that cross platform themes are really important in a RIA context and the platform dependent Look&Feel of Swing is already good. Nimbus has a very modern and bold style. At the beginning I really liked the style, but now I am concerned with the acceptance of it. Screenshots from the theme can be found on Jasper Potts blog. The implementation still has several bugs (e.g. the JTree) and a beta implementation is expected at the JavaOne 2008.

My favorite improvement is the new Applet plug-in. Applets sucked, still suck, and will … rock. Yes, really! This is only a beta implementation; nevertheless, forget the freezing browser, the 30 sec startup time, and so forth. I tried several Applets with the new Firefox 3 beta (the new plug-in is only available for Firefox 3 and IE 7). The most impressive one was on Map24. The site offers an Applet to visualize routes, allows zooming, 3D, is fairly complex, and started in under 2 seconds! Yes, coldstart. Since, this is only a beta I expect further improvements in the future. The plug-in contains many many improvements. Have a look at the release notes for more information.

If you want to know more, download the beta and experience it yourself or listen to Chet Haase talking about Java 6 update n.

Oh, one thing I forgot. Sun please rethink the names of your version, why Java 6 update 10 (or n) and not just Java 6.1??

A nice way to discover Nimbus is the SwingSet 3.

Related posts:

1. Java Applets! Dead? Rockin?
2. Javaworld about Applets and Java’s RIA future
3. Netbeans 6.1 beta review