Please join us at the new JavaWorld Q&A Forums. Your existing login will work there. The discussions here are now read-only.


JavaWorld Talkback >> 960586

Pages: 1
jwenting
stranger


Reged: 06/27/03
Posts: 20
divergence
      #32128 - 05/18/06 10:36 AM

Roedy is wrong when thinking Java will not fork disastrously and rapidly.
There are 2 groups of people who will quickly and fatally fork the platform as soon as they get the chance.

First the hardcore Linux/GPL crowd who've for years vowed to destroy Java. The best way to do that is to destroy the platform independence and WORA by rapid forking and introducing first binary and then source differences between JVM versions.

Second are the well meaning but largely ignorant people who think they've found a "bug" or want to introduce a new "feature".
Think all the people who think that == should have identical functionality to equals, people thinking that multiple inheritance a-la C++ is a swell idea, people who think Java is pass by reference and the incapability to return a reference through a method parameter is a bug.
They'll all be forking the platform too, causing more incompatible JVMs to hit the street at an alarming rate.

It'll soon be back to the bad old days of the 1980s when you had to specify your supported platforms highly explicitly and there were hundreds of such platforms around leading to developers having to choose either skyhigh development cost to release for dozens of platforms (each requiring different compilation, often code changes, and often packaging as well) or face a very small market indeed.

If that's the future of Java I'll soon be looking for another job again because I am convinced Java cannot survive in such an environment and it's as I see it the logical end result of releasing the JLS, JVMS, and standard API to the mercy of anyone interested in changing them for whatever reason.

The only way to prevent that is keeping the JLS and JVMS under the direct control of the JCP and keep in place the existing requirement to pass the compatibility test suite (which should also remain under strict control of the JCP) in order to use the name Java.
The JCP itself should remain under strict control of Sun itself to prevent it being subverted by those with an agenda which would be destructive to the platform as well.

In effect, the current situation would have to remain in place, with the possible difference that the restrictions on using the source code might be able to be relaxed and a more flexible system for submitting contributions might be put in place.


Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 1 anonymous users are browsing this forum.

Moderator:   

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 3011

Rate this topic

Jump to

Contact us JavaWorld

Powered by UBB.threads™ 6.5.5