first, this is about the Java Community Process. that means specifications for extensions to the platform, not necessarily the core (though some extensions may become part of future cores).
second, it was always possible to create GPL JVM implementations and even GPL Java Core Libraries. See the classpath project as an example. Nothing new there.
I can't get to the article, but it seems to me that Sun's veto power is over the standard. If you want to implement something strange in your GPL'd version of Java, of course it's not gonna be Java anymore:) The JCP is where you air your complaints with Java, and a lot of the times, if it's not a crackpot idea (IE other developers agree), then you can get it included in all JRE's next round.
SUN is moving toward a free certifacation test for non-profit organizations so that GPL'd programs can become certified. I think JBoss is proof that even though SUN hates that you exist, they see your right to make a GPL'd version of their specs. If you want to GPL a java implementation, you can. There has never been a problem with that. SUN has a problem when you call it Java and it isn't. Basically, they get upset when you infringe on their trademark. There are a lot of things out there now that are GPL'd and they are implementations of java. They aren't good yet, but that's because people like you spread FUD that SUN will come get you if you do it. More than likely, they would only tell you to not call it Java. Kaffe is a good example.
I think it's absolutely reasonable that SUN, where java was invented and where people truely understand java work, gets a veto power of the technology implementing new features. The number one reason I think this is that they are almost the only one implementing these new features. No one on the market but SUN has a 1.4 JVM. If you make up a feature that is gonna take a year to implement they should be able to veto it being included with the next iteration. This way you have a balance of power between developers who need features and the poor souls who have to make them work!
Wish people would stop saying that a non open Java means it can't be distributed. Wrong.
SuSE 8.0 personal came with two VM's in it. 1.1 & 1.2. They were loaded up, 1.2 was set to the path and ready to rock.
And cut the BS about opening java. People already have an awesome community process with the JCP. But, people see something as being "wrong" so at the moment they're blaming a lack of open source. It'd open up, and then all the peanuts would have to find something else to blame.
Java should not be opened, nope. Sun's doing a great job, and should be given a whole pile of credit for fostering the community that it has.
Slashdot Mirror
first, this is about the Java Community Process. that means specifications for extensions to the platform, not necessarily the core (though some extensions may become part of future cores).
second, it was always possible to create GPL JVM implementations and even GPL Java Core Libraries. See the classpath project as an example. Nothing new there.
third, note this quote:
"Sun still has veto power," Driver said.
nuff said.
Wish people would stop saying that a non open Java means it can't be distributed. Wrong.
SuSE 8.0 personal came with two VM's in it. 1.1 & 1.2. They were loaded up, 1.2 was set to the path and ready to rock.
And cut the BS about opening java.
People already have an awesome community process with the JCP. But, people see something as being "wrong" so at the moment they're blaming a lack of open source. It'd open up, and then all the peanuts would have to find something else to blame.
Java should not be opened, nope.
Sun's doing a great job, and should be given a whole pile of credit for fostering the community that it has.