This is another repost to sync up the EG observer mailing list.
- Stanley -------- Original Message -------- Subject: Re: Relationship to JSR 291 [was: Re: Bryan's comments] Date: Sat, 26 May 2007 00:25:38 +0900 From: Daniel Leuck <[EMAIL PROTECTED]> Reply-To: Java Community Process JSR #277 Expert List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Since what goes into the core SE platform is going to stick around for a while and evolve very slowly, it seems to make the most sense to define the minimal set of features possible to accomplish what needs to be accomplished to provide core modularity support in the Java platform. Adding more fanciful features on top of this minimal core should be left to the OSGi frameworks and NetBeans frameworks of the world, which are able to evolve more rapidly on top of the core. Trying to do too much in the core is a recipe for disaster since we all know that there is no going backwards once it is released, whereas focusing on the smallest set of features necessary gives us a better chance at doing it right the first time. I think this is the point that Glyn is getting at too...
I agree. We need to be far more risk averse with the core. Lets get the basics right.
