McNealy Answers: No Open Source Java
comforteagle writes "Sun CEO Scott McNealy has finally answered the long awaited question that has been on the minds of open source and Java developers. Will Sun open source Java? No. He stated today that Sun sees no solution solved from open sourcing Java that isn't already addressed."
While I agree - Java is Sun's trump card, you are quite wrong with your assertions that java is "closed" and "internal".
Please read this document for clarification.
Will.
McNealy's wrong. Open source Java is knocking at the door. And worse yet, it will run on Mono not a JVM!
C# and MSIL have a free implementation. Whether this qualifies those technologies as "open" or not depends on your definition of "open."
...no Open-Source SUN Java.
People being impatient have already generated GCJ and Kaffe working on open-source implementations of Java. Neither are yet as complete as the 'full' Java, but are in progress.
Is there a 'standard' for the Java language itself, in the same way that there is for "C#"? If not, could it be because Sun doesn't want to make it easier for Open-Source folks to create a complete implementation?...
Hacker Public Radio is our Friend
Uhh -- what? How about: "when's the last time you used NFS? OpenOffice?"
Like it or not, Sun is a big contributor to open source.
Time makes more converts than reason
I personally wasn't aware of the degree to which this was an issue until I installed FreeBSD. Sun doesn't supply a native JVM for it, and it's current license puts a lot of restrictions complicating the optimization of a free JVM for FreeBSD.
You can get it running, but you have to jump through hoops, agreeing to Sun's source license, and then downloading it from Sun's site before you can compile a version for your PC. After you apply patches created by someone that worked very hard to get the thing to run on your OS, the compile process takes a long time.
The worst part, though, is that it is slow on FreeBSD compared to other operating systems running on the same hardware. Very little can be done until Sun truly open sources Java.
The primary solution people have taken to is creating patches to solve the problems Sun's code has running on different platforms. This has several drawbacks. One is that the patches take time to develop, creating a lag in versions. The second is that the patched versions rarely get true testing, so you can only hope it works with your application, and that something unexpected doesn't surprise you down the road. Most people creating these patches don't have access to Sun's highly priced compatibility test suite.
The irony is that the compatibility Sun want's to maintain is eroded already by Sun's reluctance to both open source Java and make the test suite more accessible. This decision also decreases the platforms that Java can run on, the opposite of one of Sun's stated goals.
A lot of people take it for granted when they install a pre-compiled JVM downloaded from Sun's website on one of the operating systems Sun happens to support. Let me know, please, when Sun releases a FreeBSD JVM, and solves problems the OpenBSD people have had getting it to run correctly.
Open Standards Portal
The license does not prohibit redistribution. Debian has just decided the license doesn't suit them is all. That's Debian's issue not Sun's.
For the record here are the re-distribution clauses from the 1.4.2_04JDK:
Linux VPS hosting *with* Sun JVMs
Did you actually read it? People can sue Debian for faults they get when running their Sun implemented Java programs. That clause is revolting.
Comment removed based on user account deletion
That's right. People can sue Debian for problems with Sun's software. People can also sue Debian if there is a bug in the Linux kernel. Or a problem with any other software package.
Debian distribute their distro. They are responsible for it.
No doubt they 'pass the buck' with their own clause indemnifying themselves in the event of any problem.
> 1) You can make your own java compiler.
> 2) You can make your own JVM.
> 3) You can make your own libraries.
> 4) Your java code can be open source.
All these things are true, but the one thing you can't do freely is call any of these things "Java(tm)". That requires having your product pass compliance testing and be certified *by Sun*. The compliance kits are not free (in either sense) and the certification process has a price tag attached as well.
This may not seem like a big deal to the individual user or developer, but when dealing with the corporate world you're nobody unless you have that squiggly coffee-cup logo and the "(tm)". The end result is that if you want to play the Java game, you have to play (and pay) by Sun's rules.
Drinking will help us plan!
I used up all my sick days, so I'm calling in dead.