Plog

Interesting news:
http://digg.com/software/Update:_Sun_to_open-source_Java

My concerns exactly. I could not continue to develop Java code if there were two or more of any of the following:

• Incompatible compilers (with different grammars)
• Varying or inconsistent class libraries
• Variety of JVMs for the same platform (MS Java was headache enough)

Now this is only considering popular derivatives (say over 5% fragmentation).

However if they manage to prevent fragmentation of the language, this would place Java in a good position to start getting:

• Faster pace with new C# 3.0 features: Anonymous Methods / Language-DB Integration
• Faster pace to catch up with .NET base features: Properties / Newer Javadoc / Language Derivatives using same VM
• Fewer divergent development paths (SE vs EE development - Why Two?)

Yet at the same time all of this can be done through the JCP

• Keeping language features held down by a slow moving group prevents isolating the language from new users. KISS?
• Helps prevent too fast versioning or releases for no particular reason
• Better agreement on proposed features instead of just programmer centric reasons

To me that last point is one of the most dangerous avenues of open source. One example of this is like the Find Toolbar in Firefox. No-one asked for it and it certainly doesn’t save anyone time, yet it replaced a find dialog that most people are used to, can search in text fields, and has more options (whole words, case sensing, and repeat find without seeing the box). Yet we will probably never get the old search back because of that one un-voted for change. If things like this happen to Java it will scare the hell out of me.

For example if many C# developers get their hands on it they might change from the getCamel/setCamel to property Camel { get {… The problem is that the language could fracture the community if the development is not voted for.