Simon Phipps on the Process of Opening Java

twofish writes "Simon Phipps, the chief open-source officer at Sun Microsystems, has reaffirmed Sun's commitment to Open Source in an interview with computerworld. The focus of the interview is Simon's efforts to fully open source Java. He points out that many problems need to be resolved before Java can be open sourced — ownership, legal, access, encumbrances and relationships with Java licensees. It took Sun a full five years to solve these issues with Solaris. However Simon predicts that it won't take anything near this amount of time to complete the task with Java. Of course, one of the other concerns for OS Java is the resulting incompatible versions and breaking of the Java WORA model (Gosling himself has always been particularly concerned about incompatible forks resulting in the introduction of an open source version of Java) and this opens up additional problems for the open source Java model."

Comments

Incompatible Java forks

[Anonymous Coward]

Gosling himself has always been particularly concerned about incompatible forks resulting in the introduction of an open source version of Java)

So hold onto the trademark, the same way the Mozilla foundation do, and only let implementations that pass a rigorous testsuite use it.

Re:Incompatible Java forks

[Brandybuck]

To play devil's advocate, I think what they're worried about is another J++, where someone (Microsoft) creates an almost-but-not-quite Java, and then you end up with "write once run nowhere else". I don't necessarily agree with that worry, but I strongly suspect that's what's in Sun's head.

Re:Incompatible Java forks

[Bogtha]

I think what they're worried about is another J++, where someone (Microsoft) creates an almost-but-not-quite Java

Which of these two scenarios do you think is most likely to cause that situation?

• People who object to Sun's non-open license create a from-scratch implementation of Java, or
• People take Sun's open-source Java and use it directly.

It seems fairly obvious to me that forcing people to create another Java implementation instead of letting them use the "canonical version" as they wish is far more likely to bring about another J++ situation.

Java already breaks the WORA model

[MarkByers]

I have a Java client on my webserver and half the mails I get are because the Java client doesn't work on people's computer. Usually this is because they have some old version of Microsoft's Java Runtime installed, which only supports Java 1.1 (badly).

What a mess! I can't really see how opening it up will make it any worse than it already is today.

Re:Java already breaks the WORA model

[99BottlesOfBeerInMyF]

Usually this is because they have some old version of Microsoft's Java Runtime installed, which only supports Java 1.1 (badly). What a mess! I can't really see how opening it up will make it any worse than it already is today.

Okay so MS broke the law and released an intentionally broken JVM to try and kill Java as a dev platform. The courts stopped them, but you're still dealing with the mess with a few remaining legacy systems from that time. You don't see how giving MS an opportunity to bundle a new broken version on every computer sold in the world could make things worse?

Re:Java already breaks the WORA model

[Decaff]

I have a Java client on my webserver and half the mails I get are because the Java client doesn't work on people's computer. Usually this is because they have some old version of Microsoft's Java Runtime installed, which only supports Java 1.1 (badly).

What a mess! I can't really see how opening it up will make it any worse than it already is today.

Guess what! I have some Linux software that won't run on the 1.0.x kernel or with really early versions of libc. By the same reasoning this must surely mean that Linux is broken and you can't write the same code for different platforms.

Of course this is nonsense, and isn't what WORA is about, and certainly shouldn't have been rated 'insightful'. WORA does not include some kind of time machine facility to allow software written to current VM and language and library specifications to work on 10-year old VMs and old libraries. The idea is, of course, that if you write for Java 1.4.2, your software will run on any Java 1.4.2 VM (or later) on any platform.

Other Open Source languages don't seem to suffer

[Burdell]

There are many open source programming languages already (perl, python,
etc.), and they don't seem to have a problem with forking or
compatibility.

If Sun fosters a good development community, there shouldn't be a
problem.

Exactly

[sterno]

It is fair to say that down the line even when they do opensource it, Sun's version will be the defacto standard. Figure if they and IBM work together on new versions, there's a pretty good guarantee that there won't be any major forks. Sure, there will be forks, but invariably those forks won't be what the average corporate server is running on, etc. Since it's open source, any of the good changes from those forks can be rolled back into the main Sun standard.

I can understand Sun's fear as Java has been a huge part of their business, but I think as long as they keep pushing the standard forward forks will be irrelevant.

Solaris - solved?

[kripkenstein]

It took Sun a full five years to solve these issues with Solaris.

Solved? We should be so lucky. Things are far from solved. If Sun had released Solaris under the GPL, that would be good and done. Instead, it's under their own CDDL, which isn't easily compatible with the far-more-common GPL. This leads to issues for interesting projects like GNU/Solaris (Nexenta), which should have been quickly welcomed by the Open Source community. Instead, Sun's choice of the CDDL makes things complicated where they shouldn't be.

So, in short, I would not say that Sun 'solved' these 'problems' with Solaris, and I sincerely hope they do a better job with Java.

Re:Solaris - solved?

[kripkenstein]

You're pointing at a problem that to Sun wasn't a problem. They *WEREN'T* aming for GPL compatibility.

I guess they weren't, since they didn't. And this is certainly a problem for the Open Source community. But this is also a problem for *Sun*, I would argue. What are the chances of OpenSolaris taking off, if the vast majority of the Open Source community can't use its code with the code they are used to? They can't improve OpenSolaris as they would like, and vice versa.

The whole CDDL issue seems to be an attempt to challenge Linux. Perhaps they envision a 'two-power' future for Open Source, where there is the GNU/Linux camp, under the GPL, and the Solaris camp, under the CDDL, and no code shall pass between them. This sounds a bit like the cold war to me (but maybe I'm just too old and/or senile, and mixing my metaphors).

To get back to the point, Sun open-sourced Solaris at a time when there was already a large and fruitful Open Source community. They chose not to play nice with that community, and seem to want to start a new base of power. If this is their 'solution', I'm not sure what the problem was. I find it hard to envision a promising future for OpenSolaris under current conditions.

That's a popular method.

[jd]

• The "red book" that defined the CD standard was the main reason CDs were as interchangable as they were. DVDs, which have no such rigorous standard to meet, tend to be less predictable.
  
• IPv6 hasn't got an "official" centrally-run test suite, but such suites for the purpose of certification do exist.
  
• C follows standards, rather than official regression tests, so you do get a lot more variation in quality and interchangability. In general, though, it demonstrates that simply defining a central standard is adequate for basic stuff.
  
• POSIX used a mix of standards and official testing, and had a big impact on the interoperability of Unix systems - though nowhere near as much as seems to have been hoped.
  
• Standards and tests by committee seem to be a Very Bad Idea. CORBA and SQL followed this road and have resulted in guaranteed inefficiency - apparently for the purpose of promoting the "extended" packages released by the vendors who created the standards in the first place.
  

If the process is followed - hey, that's great, but is needs to be done right if it is to be worth the doing.

Re:As a web app developer...

[Brandybuck]

Just because all you have is a hammer does not mean that every problem is a nail.

Who will fund future development?

[Kunta Kinte]

My main concern with Java being Open-Sourced is that Sun may lose its incentive to continue funding Java development.

Java is not Python nor Perl. Even then, how long has Perl6 been in development? "It's ready when it's ready" is not good enough to much of the corporate world.

People asking for Java to be open-sourced believe that this will increase the amount of resources put into Java. I'm not so sure.