I've been trying to understand if the proposed modular JRE architecture will bring any benefits to those who predominantly develop sever-side applications. I can imagine that startup times might be slightly reduced, potentially memory footprint might be reduced, but other than that I can't see many big advantages. On the down side, I imagine that there will be more application failures when an app that appears to be working tries to access a library that isn't in this particular installation. I've heard all about how the JRE might go and download the components it needs, on demand; to which I respond .. not in my secure hosting environment you won't.
Is my FUD here misplaced? Are we really trading the security of the traditional server-side Java stalwarts to make Java more attractive on the client side? I'm sure that there'll be an 'All-in-one' download available - I'm also sure that I've lost times of the occasions when an SA, with profound knowlege of UNIX, but little knowledge of Java, installed a JRE instead of a JDK. Adding more choices can't make life easier for them, and by extension .. me. It is, of course, certainly possible that I'm getting nervous over nothing. R. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The 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 -~----------~----~----~----~------~----~------~--~---
