Eric S. Raymond, president of the Open Source Initiative, said in an open letter last week that Sun needs to choose between controlling Java and seeing it spread as widely as possible.
"Sun's insistence on continuing tight control of the Java code has damaged Sun's long-term interests by throttling acceptance of the language in the open-source community, ceding the field [and probably the future] to scripting-language competitors like Python and Perl," Raymond said in the letter.
"The choice is between control and ubiquity, and despite your claim that 'open source is our friend,' Sun appears to be choosing control," he said. "Sun's terms are so restrictive that Linux distributions cannot even include Java binaries for use as a browser plug-in, let alone as a stand-alone development tool."
Raymond's remarks were in response to a speech in which McNealy said, "the open-source model is our friend." The chief executive argued that Sun is better able than competitors to withstand the advent of open-source software, which can be obtained at no cost.
Sun responded to Raymond that it has struck the right balance between releasing control of Java and running the risk that a company such as Microsoft could undermine the software. Java lets the same program run on many different types of computers, undermining the significance of a particular operating system such as Windows. Sun and Microsoft have fought years of legal wars about Microsoft's treatment of Java.
"There is a trade-off between protecting Java from misuse and allowing as many people as possible to contribute," Russ Castronovo, a Sun spokesman, said on Friday. The Java Community Process, a formal structure by which companies such as Motorola and IBM have a major say in the future of Java, "works very well," he said.
Java is indeed a very different creature from open-source software, said Shawn Willett of Current Analysis. "At its heart, Java is something that you're going to pay for," and its development is dominated by companies with a financial interest in its success.
But while Sun might do well to listen to complaints from open-source programmers about Java's licensing terms, the company probably doesn't need to worry about one of Raymond's predictions, Willett said. "I don't think Python is going to take over Java. Java is the language to learn. There's an infrastructure set up where people get trained in Java. People do, because they know they'll get jobs that will pay them well."
Sun has been adjusting Java to open-source groups. For example, in 2003, it hammered out a truce, under which open-source Java group JBoss would get access to Sun's Java compatibility test software.
Raymond is the author of an influential essay on open-source programming, titled "The Cathedral and the Bazaar," and more recently of a document disputing the SCO Group's claims that Linux infringes on Unix intellectual property.
Raymond praised Sun for releasing specifications for the Network File System software for sharing files over a network and for opening the source code of the OpenOffice.org competitor to Microsoft's Office suite. However, he said, Sun's technologically superior NeWS graphical interface for Unix lost out to the X Window System, because the latter was open-source software.
"If Sun were prepared to go all the way with open source, it could seize back its position of industry leadership [and] do even better than IBM has from a full-fledged alliance with the open-source community," Raymond said.






Talkback
Sun being a control freak company, that's unlikely to happen. They still don't understand that they can opensource and still trademark and more importantly, control the life of the project.
Java could become the application run-time layer in linux, making underlying distros differences less disruptive and allowing plugins to be developped for better hardware control from Java.
Java is a specification of a language and not the properly told language.
IBM implements the specification and has your Java Virtual Machine.
Sun implements the specification and has your Java Virtual Machine.
GNU implements the specification and has your Java Virtual Machine.
Oracle implements the specification and has your Java Virtual Machine.
I can use any a destas implementations (of any manufacturer) to run my program that I develop in Java. I do not be arrested to none of these manufacturers. my program is going to run in quaquer Java Virtual Machine (Interpreter) of any manufacturer, since they really implement the specification.
Each manufacturer has a different license for each implementation that he does. It is the license that imports.
Who is responsible for Java's Evolution is the community: and it is not any of these manufacturers. The specification is defined in .
The answer to Scott McNealey's fears that Microsoft or anyone else will abuse or tamper with Java code after it's release to the Open Source community, is to make sure that, like Linux, it is released under GPL.
If it is done that way as well as having a proper standards board set up under the auspices of e.g. OSDL, then the rigour of the OS community scrutiny and feedback on common IDE etc., will ensure it's success as an effective OS answer to .NET.
Because of the "ease of use", seamless computing, global Web services and application driven nature of .NET, it is a far greater threat to OS, competition and freedom of choice in the IT industry than Windows. As has been proved with Linux on the operating system and infrastructure front, the only effective answer to Microsoft on the application and services front is an OS community owned and standards based Java.