Jigsaw Feedback Roundup
The JavaOne tech keynote demo of Jigsaw inspired a bunch of feedback on blogs:

Alex Miller thinks the vision is pretty coherent:

The more I saw of this talk, the more I realize the scope here is ambitious - there is a pretty coherent vision in this demo and it’s broader reaching than I had previously understood. The vision includes a complete overhaul of how we compile, package, and startup our Java applications.

Peter Pilgrim thinks it made common sense:

I was particularly impressed with the Project Jigsaw, the JDK modularisation effort going since Christmas last year. At Devoxx, Reinhold just talked about it, at this year's JavaOne conference, he demonstrated it with Ubuntu Jaunty Jakolope. The first that vowed was the removable of the CLASSPATH that had the crowd in "oohs and aahs". Reinhold show the JDK can be pulled from Ubuntu repository in stages and the JMOD command. He built a simple application that required the installation of the compilation, awt and swing modules. Jigsaw finally made a lot of common sense.

Bram Bruneel was impressed by the native package generation:

Further more Mark showed us a nice demo of the packaging and distribution of Java apps on ubuntu. De JDK modules will be normal debian packages and you will be able to create your own Java application, export it to a debian package and define a dependency towards the java modules you need to run your app. Quite nice.

Gerard Davison looks forward to a future without mandatory CORBA downloads:

The one significant project was "Jigsaw" which reduces the JDK into much smaller modules. For example desktop profile made up of base; awt and swing. Really does cut down on the core download. Oh for the day we don't have to download the Corba support all those useless classes which pollute code insight.

Floris Ouwendijk thought the keynote demo was very clear on the functionality of Jigsaw:

Mark Reinhold took over the presentation to discuss the JDK7 features. The focus is on modularity and multi-lingual capabilities. The modularity features (project Jigsaw) are intended to decrease download size for people without broadband (apparently more than a few), as well as supporting constrained devices. He performed a lengthy but very clear demonstration of the functionality provided by Jigsaw.

Augusto Sellhorn has a good post summarizing all the Jigsaw related sessions:

The main reasons to introduce Jigsaw into JDK 7 are the following:

* Eliminate classpath complexity (classpath/jar hell problem already discussed).
* Increase performance. The VM download size can be made smaller, and startup time should improve because for small programs (say HelloWorld) unnecessary classes don’t have to be loaded at all. Mark showed how he could run HelloWorld by only using 2 modules listed by the new jmod command; jdk.base@7-ea and jdk.boot@7-ea.
* Enable native integration for installing modules.

Peter Kriens likes the native package generation for the JDK, but doesn't want to have to see it:

Then about Jigsaw. It is very focused on breaking up the JDK into modules. I like the native installers but I dislike the fact that they put this native packaging stuff in my face.

Jason Young thinks Jigsaw was a JavaOne highlight:

Highlights from my perspective:
* Project Jigsaw (Java 7 modules) – the modularization of the JVM and application libraries has a lot of promise, and can help cut down on bloat. The keynote demo of this went well.

Eric Newcomer uncloaks as a resident jigsaw-dev lurker:

One more thing to add - I have been following the Project Jigsaw public email list, and from what I could gather what was presented at Java One was more or less equivalent to what they could manage to get done by then.

And if you've really made it all the way down here, then let me point you to the latest JavaPosse interview from JavaOne with Mark Reinhold and Alex Buckley, about Jigsaw and JSR 294.