On 7/22/2012 12:45 AM, Reinier Zwitserloot wrote:
On Saturday, July 21, 2012 2:29:00 PM UTC+2, JessHolle wrote:
What about modularizing the JVM? That's only important to allowing
the Java SE codebase to be more readily re-used in other
environments -- and /possibly/will yield faster startup time
(though a good refactoring could likely do that by itself).
Modularizing a fairly large program usually leads, down the road, to a
project with better code quality, less bugs, and all that. That's one
more thing to chalk on the 'pro' side of jigsaw. Also why delaying it
is acceptable to me, if the conclusion is that this can't be done
properly in time for java8.
Modularization of the JVM itself can be delayed without any real issue
from my perspective.
Same goes for native packaging integration (though how is it that Java
still doesn't have a standard Windows service wrapper!?!).
Getting a simple all-in-one build-time and runtime module system
integrated into the language, however, is key and /far/ more important.
That piece should come in Java 8 -- without the rest of the less
critical, and thus distracting, stuff.
--
Jess Holle
--
You received this message because you are subscribed to the Google Groups "Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
