Opinion: OSCON attendees seem more interested in Java than Solaris, and Sun's best move could be giving them what they want.

Earlier this month, I attended the O'Reilly Open Source Convention in Portland, where I discovered a great fast-food place called Burgerville and was absolutely dazzled by Damian Conway and his talk, "Fun with Dead Languages."

During the talk, he demonstrated (with running code) the syntactic benefits of developing in Latin.

Beyond double cheeseburgers and dead languages, one of the most interesting themes for me at OSCON was that of companies and developers struggling to figure out how best to digest—or at least plug into—the processes and licensing frameworks that comprise free and open-source software.

Not surprisingly, OSCON attendees seemed convinced of the quality of particular free and open-source software projects, and of the general benefits of the open-source development model, but the potential loss of control that comes with open source is tough for many to swallow.

For me, and for many of the attendees I talked with, one of the most fascinating examples of a company coming to terms with open source is Sun.

This year's OSCON was OpenSolaris' coming out party. Sun employees were out in force, sporting tasteful (by tech apparel standards) OpenSolaris t-shirts. The conference also featured a bunch of OpenSolaris-oriented sessions.

Read more here about Sun Microsystems' OpenSolaris project.

However, the people at the conference were talking more about Java's open-source prospects than about Solaris' prospects.

After all, the conference attendees seemed to be mostly developers, not operating system people, and developers rely more on Java for their livelihoods than on Solaris.

Sun President Jonathan Schwartz made an appearance during the big mid-week keynotes, where he repeated the current Sun line on open-source Java: Sun is opposed to an open-source Java for fear of forking.

Click here to read more about Sun's plans for the future of Java.

What's interesting, though, is that beating back the calls for an open-source Java looks to be the surest way to ensure that Java forks—and the forking has already begun.

On the same day that I watched Schwartz express his concern over a Java divided, I attended a talk given by IBM's Geir Magnusson on the Harmony project.

Harmony is an effort within the Apache group to create a compatible, independent implementation of J2SE 5, and of the Java runtime, under the open-source Apache License.

The next day, I attended a session held by Red Hat's Tom Tromey, who spoke on the state of free JVMs.

These sessions boiled down to three basic points:

Java, as it's currently licensed, is relegated to second-class-citizen status on open-source platforms. Anyone who acquires a copy of Debian, Fedora or pretty much any other Linux distribution can expect immediate access to a host of popular development languages and runtimes, none of which are Java; it's not surprising that so few open-source applications—particularly on the desktop—are written in Java.

Compare this to the open-source implementation of .Net, Mono, which has rapidly begun accruing interesting new applications.

Individuals and organizations are putting significant effort toward making open-source Java a reality. Large IT vendors and individual developers alike have quite a bit invested in Java, and they're willing to do what it takes to arrive at a Java implementation free of its current distribution limitations.

There's quite a bit of work left to do. While the forces for free Java seem determined to loosen those chains, the shortest path—by far—to a liberated Java would still run through Sun. To its credit, Sun has already taken steps, in the latest version of its Java license, toward making an open-source implementation of Java possible.

Sun should reconsider its stance, however, against taking a more active role in the effort. Sun's interested in maintaining a certain level of control over Java, but by gripping it too tightly, the company may eventually lose that control.

That's because, once a free and complete implementation of Java does exist, its redistribution advantages will give it a competitive edge over Sun's official implementation.

If Java were invented today, would it go anywhere if it wasn't freely licensed? I think the clear answer is no, and I think that Sun, as an organization, realizes this as well.

Senior Analyst Jason Brooks can be reached at jason_brooks@ziffdavis.com.

This article was originally published on eWEEK.com.

Discuss Free Java: Sun Struggles to Come to Terms with Open Source   >>> Be the FIRST to comment on this article!

>>> More Languages Articles          >>> More By DevSource