Linked by Thom Holwerda on Mon 13th Nov 2006 08:46 UTC, submitted by someone
Thread beginning with comment 181901
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Yep, JCP and Sun will have the last word. For now. And that is a good thing. You really don't want every programmer under the sun to put what he/she likes in Java. However, that JCP and Sun governance will have to morph into something more practical down the road (if too many people are unhappy with the way Sun/JCP lead things, they will fork).
On why Apache wasn't choosen; first of all, it doesn't play well with GPL (read, Linux). Second, you don't have to give code back.






Member since:
2005-07-09
...is how it is going to be decided what code is going to go in and what is going to be rejected. I mean in the iedal world, going open source and gpl'd and all that means there is now a much easier access of the code by hugely talented programmers. But is there going to be a body finally that will decide what goes in and what doesnt? A colleague of mine asked me why they didnt go with ASF (Apache Software Foundation) because they have a very well known track record for producing excellent quality code. Does it mean that GPLing the code means anyone can get access to it but that if someone wants to add the next hot feature, Sun and its JCP still will have the final say? Sorry if I got my terminology etc incorrect. Just trying to understand. Thanks.