Slashdot Log In
Sun to Release Java Source Code
Posted by
ScuttleMonkey
on Tue May 16, 2006 02:53 PM
from the long-time-coming dept.
from the long-time-coming dept.
pete314 writes "After resisting for years, Sun Microsystems CEO Jonathan Schwartz at JavaOne this morning said that he will release the source code for Java. The company is asking developers to provide feedback on how to best get there and prevent forking and fragmentation."
Related Stories
[+]
Linux: Sun Puts its Weight Behind Ubuntu Linux 338 comments
fak3r writes "Sun today announced that they are putting their weight behind Ubuntu Linux. While Ubuntu has been many people's desktop Linux choice for a few years now, with its Debian heritage, you can see what kind of server it could be. Slap that on the new Sun 1Us with the new Niagra T1's CPU, the one that'll have four, six or eight cores each, and go to town."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Misleading Headline (Score:5, Informative)
(http://www.intelligentblogger.com/ | Last Journal: Monday August 27, @11:47AM)
BZZT! WRONG! Java source code has been available for YEARS! (And no, I'm not going to bother linking. If you don't already know where to find the SCSL and JRL licensed code by now, you need to pull your head out of your butt and Google it.)
This article is nothing but a blurb that suggests that Sun is looking at Open Sourcing Java. (What the Slashdot pundits have been screaming for, for years now.) Unfortunately, one of OSI's core requirements is forking. So Java will never be able to make the pundits happy.
Re:Misleading Headline (Score:5, Insightful)
(http://jedidiah.stuff.gen.nz/wp/ | Last Journal: Wednesday April 04 2007, @02:51PM)
Sure they can - there are other ways to pevent forking than in the license. Look at most of the major OSS projects around and you'll see that there is very little in the way of forking - sure minor forks exist but they quickly die. Sun doesn't care about some minor fork of Java that 20 people use that eventually dies, they are worried about a significant competing standard that honestly splits developers between two different platforms. How often has that happened with big OSS projects? Hardly ever. The question is not so much "what can be done to prevent forking" but "what happens that causes a successful fork". The major examples of significant splits in the OSS world would be Emacs/XEmacs, gcc/ecgs, and XFree86/Xorg. In each of those cases the reason for both the fork, and the success of the fork, comes down to the original project stagnating and being unresponsive to change. Avoid that and you tend to avoid significant forks.
Jedidiah.
Re:Misleading Headline (Score:5, Insightful)
(http://www.intelligentblogger.com/ | Last Journal: Monday August 27, @11:47AM)
But they DO care about IBM or Microsoft creating a VM that advertises compatbility, but actually pulls the bait-and-switch routine. Remember, Microsoft already tried to pull that routine with the NON-OSS version of Java. It was the license that stopped them. This time, you can be sure that they would stay precisely inside the letter of the law. No Java trademarking, but no compatability testing either. Companies will start to rely on it for its Windows performance, and then Microsoft will start introducing subtle differences. Before you know it, users will blame Sun for being incompatible.
Re:IBM? Microsoft? (Score:5, Insightful)
(http://www.faqs.org/rfcs/rfc3675.html)
I think the last thing Microsoft wants to do right now is to put "lots of bugs == bad" into people's minds.
Re:Misleading Headline (Score:4, Insightful)
(http://jedidiah.stuff.gen.nz/wp/ | Last Journal: Wednesday April 04 2007, @02:51PM)
Jedidiah.
Re:Misleading Headline (Score:5, Informative)
(http://www.intelligentblogger.com/ | Last Journal: Monday August 27, @11:47AM)
WindBourne! I'm shocked to hear such garbage from you!
Current "Stable" JVM - <= 1.5 [sun.com] (SCSL)
"Unstable" JVM Branch - 1.6 [java.net] (JRL)
Every, (and I do mean every) story on Java here on Slashdot has contained one of those two links. Most of them contain BOTH. Why? Because the trolls come out in force. The fact that you didn't take the time to look into the matter (I believe I suggested Googling for it) is disappointing and disheartening.
Re:Misleading Headline (Score:5, Insightful)
(Last Journal: Monday November 12, @02:31PM)
There's a more interesting issue here. Sun Java is an embarassment to the OSI. Over the last few years, by using a community driven development process, Java has improved leaps and bounds. Essentially, Sun said "What the Open Source movement says is right, except for the freedom part". And given the OSI keeps being at pains to argue that it's merely a front for software freedom, trying to encourage the development of free software by promoting community-driven development processes which, supposedly, rely upon the software being developed to be Free, this really doesn't hasn't helped it much.
Essentially, the OSI says "We must have free software, because free software means a community of interested parties can develop a program to a much higher standard than would otherwise be the case if it was proprietary. We describe this whole thing as "Open Source"."
Sun responds with: "Aha! But Java isn't free, and it too is developed by a community of interested parties, and they've generated a much higher standard of product than would otherwise have been the case if it wasn't developed using a community process. So your argument fails because you don't need software to be free to use your "open source" development model!"
ESR responds with: "You all suck. Set Java free!!!1!"
So why's Sun "open sourcing" Java? I think they're just looking at ensuring the official Sun implementation has wider adoption, by removing licensing barriers. Free software licenses happen to be a great way to get there. Sun wants to get Java "out there", especially with .NET nipping at its heels. The real problem with Sun's strategy hasn't been forsaking the development model advantages of the OSI's "Open Source", it's been that it's harder to integrate the official Sun Java, the reference implementation, with the non-Java world, because of licensing issues.
And as such, I don't think Sun gives a rats arse what the OSI thinks.
FWIW, I wrote about this in my journal [slashdot.org].
Re:Misleading Headline (Score:4, Interesting)
Sun doesn't support Java on Linux. Open sourcers complain. Now, they do, thanks to open sourcers complaining.
Sun didn't support Java on Linux because of open source pressure. They supported it because Linux was very successful commercially and so needed an implementation of the primary commercial development language - Java.
Sun doesn't support Java on Linux as a tier-1 platform. Open sourcers complain. Now, they do, thanks to open sourcers complaining.
Which is complete nonsense. Sun have supported Java on Linux as a primary platform for a very long time.
Sun doesn't release source code for Java. Open sourcers complain. Now, they do, thanks to open sourcers copmlaining.
You need to have a far better understanding of Linux and Java history.
I really don't think you understand how little open source matters in this respect. Java is already the number one development language in almost all areas of development - open source, server side, commercial application development. Sun has open sourced more lines of code in the past year than any other organisation - the entire Solaris codebase, and now they are doing this for Java. However, unless they deliver the entire source code as GPL directly to Richard Stallman, along with a grovelling apology for ever having doubted the true open source faith, some people will never be satisfied!
Its Simple (Score:5, Funny)
(Last Journal: Thursday November 11 2004, @12:40PM)
Less talkin' more openin' (Score:2, Insightful)
(http://whineymacfanboy.googlepages.com/ | Last Journal: Thursday April 12 2007, @09:28AM)
I know, I know, Sun's afraid that Eclipse is going to... well eclipse the sun, but c'mon! make it GPL, retain the trademark and you won't believe the explosion in Java coding you'll see!
Re:GPL'ing java would be bad... (Score:5, Informative)
You can't prevent it. (Score:2, Insightful)
I guess it doesn't *have* to happen, but there seem to be more than enough people that want to take Java away from Sun that it's inevitable.
C'mon Jeanie! *Please* get back in your bottle! (Score:5, Insightful)
(Last Journal: Monday April 03 2006, @07:23PM)
Well, as a developer, I will tell you THE one and only way to prevent forking and fragmentation...
Don't release the source code.
Oops.
How to prevent forking and fragmentation (Score:4, Insightful)
Change the title (Score:5, Insightful)
Trademark usage. (Score:4, Insightful)
You want to prevent forking? (Score:5, Insightful)
(http://evilempire.ath.cx/)
Look at Perl. It's open source, and hasn't really forked. It has, however, evolved.
"Look at Perl." (Score:5, Funny)
(Last Journal: Sunday November 06 2005, @05:24PM)
Re:You want to prevent forking? (Score:4, Insightful)
There are also raging debates over how certain numerics extensions should be done. You could argue that a minor fork has already happened with logging. Some people have a strong preference for Log4j over the Java API.
You get three or four examples of good but different forks, and Java as a stable, uniform platform could be in trouble.
You can only use the term "Java" if you pass tests (Score:5, Insightful)
(http://www.geoffrobinson.net/)
This may not be a GPL license, but that's alright.
Is there any reason why such an approach wouldn't work?
Criteria #1 (Score:3, Insightful)
Just don't break it, please (Score:3, Funny)
Java and the DISPLAY variable (Score:1)
My favorite Java feature is that it works well when you export the DISPLAY.
Some excellent examples of this are
Java in Mozilla, OpenOffice, Veritas NetBackup and UGS TeamCenter products.
I too think that it's important that Java does not get forked.
Oh well, that my 2 cents.
The Media Is Retarded (Score:2)
Why is this a surprise? (Score:5, Insightful)
(Note that I don't use "geek" derogatorily as I fondly consider myself to be one.)
Sun is giving us a ton of surprises in the past few years with Schwartz on board - from AMD processors to their first, AFFORDABLE powerhouse workstations (Ultra 20). I'm not surprised by this move at all, but I also don't blame them for wanting to be able to protect one of their revenue streams. At least Sun is trying. I guess the Slashdot "make it free or forget it" is still too strong, based on the responses I've seen so far in this thread. Looks like when it comes to Java, Sun is damned whether they do or don't. Pity.
I can hear it now... (Score:1, Redundant)
(http://marciandgreg.com/ | Last Journal: Wednesday January 07 2004, @07:30PM)
okok, but why (Score:2)
How? Three words: (Score:2, Interesting)
(http://tom.digitalelite.com/)
Seriously, there's a reason it's so popular. It ensures that noone can hijack the project and the source code will be legitimately free. You will make the most people happy with your decision if you go that route. Anything else will be seen as hedging your bets.
Tom Caudron
http://tom.digitalelite.com/ [digitalelite.com]
When and If this happens... (Score:2)
(Last Journal: Tuesday May 25 2004, @12:56PM)
I'd say that this is a classic situation where Java will not be the only thing worth studying. Once the license is decided and the code is even more out there for even more possibilities will we see IBM do even more with it? Will we see schools teach more Java because it has passed open source muster? Will this help it gain market share? Force M$ to open its languages? What about a new free Delphi?
I hope everyone, including Sun, is pleased with the outcome of this. Its not everyday such a big player takes this step. What do people think will happen?
We'll have to see.
LS
forks are good (Score:1)
Twenty years ago people were all the time telling me that the biggest problem with unix was all the different versions, nobody was ever gonna use it if they couldn't be certain tht the version they picked will still be around in ten years. They were for the most part MVS bigots (or CDC cybernaughts).
I've heard a lot of the same stuff 'bout linux, mostly from windows washers.
This talk about forks doing harm to java is pretty much the same type of FUD.
I just see Emily Latella saying "Forks are good! I think there should be more forks. Just imagine how much more the Chinese could have contributed if they hadn't spent so much time fumbling around with those chopsticks..." Finaly, Chevy leans over and whispers "fork me"
YES (Score:3, Funny)
(Last Journal: Monday May 17 2004, @07:10PM)
In other news.. (Score:4, Funny)
Open Source? Nah... (Score:2, Insightful)
I don't care one bit about Sun Java as open source. Sure, it could be nice, but do you really think that a great number of amazing programmers would eagerly step up and immediately start to maintain and improve Java? And in that doing a better job than Sun & JCP is doing right now? Don't think so...
However, there is one thing Sun could do... one very important thing: remove the stupid click-through license on downloading the Java source-code. That one thing would mean that the BSD portstree or Gentoo portage could build Java from source - unsupervised. Today it's a total pain to manually download a bunch of distfiles. Even the patches can't be distributed without a click-through license. That sucks.
But then ofcourse, legal redistribution of Java binaries wouldn't hurt either...
But Open Source Java? Nah... Not really needed.
At this late date, who cares. (Score:4, Insightful)
(http://www.whiteboxlinux.org/)
Even today's new initiative to loosen the binary license to permit distribution repackaging is being being greeted by a certain amount of scepticism just because it is Sun. Personally I'll believe it is for real (as opposed to a deal for certain select popular distros, much like the Firefox trademark bullcrap) if jpackage.org can finally ship a binary rpm.
TeX (Score:4, Informative)
Still has Unacceptable Terms! (Score:2)
(http://www.1407.org/~rms)
So Ubuntu can't package it in such a way that gcj and java reside on the same system (forget alternatives)
So Mark Shuttleworth must have been quoted before reading. Sorry Mark, Sun tried to fool you and the Free Software community!
At this time, I stopped reading the license [java.net] as it's irrelevant. gcj is turning proprietary java irrelevant by the day.
GPL + DFSG compatible (Score:1)
forking is good (Score:1, Flamebait)
(Last Journal: Sunday October 28, @11:25AM)
everytime java activates, my computer slows down.
why shd i put up with this ?
Why is Linux forking considered a bad thing? (Score:3, Interesting)
(http://www.visi.com/~rsteiner | Last Journal: Friday August 04 2006, @12:01PM)
That's the beauty of being able to fork the code -- people can use it as the basis for scratching their own itch.
The freedom to fork Linux distributions has resulted in something that most markets identify as "competition", something which the x86 desktop OS market hasn't seen in some time.
In spite of Sun's touching concerns, this can actually be a healthy situation, and usually is.
I suppose this will end Java innovation for me (Score:2)
I expect java will fork a few times, then the forks will fork. It will quickly descend into dozens of incompatible custom builds while those who want to get work done stick with 1.5 or 2.0 or whatever sun ends with.
I imagine an official sun build going forward for a while--pulling along behind it an ever-increasing pile of hanging-on junk projects. Eventually it will lose it's steam because of the fragmentation of the user base and the requests to "Keep up" with features in these side versions until it grinds to a complete halt.
All this time, committees will be adding "Features" that sun has been holding off on. Features that might save a programmer two keystrokes or allow some trixy maneuver while sacrificing "just a little" readability (like Generics did--IMO sun is already moving too fast!).
I guess now I'll start the search for the next beautiful language that can pull itself up above the fray--above the garbage that is the syntax of Ruby, C++, VB and all these other pretenders.
I suppose that it is possible that Sun will manage to keep control over the language definition via licensing, but I'm not going to hold my breath.
It's been fun.
fragmentation is the point of open source! (Score:1)
Sun is right to fear fragmentation; the minute they open source Java, they will lose control. Personally, I think that's a good thing for Java. but Java zealots disagree. In any case, I stopped worrying about it. It's taken Java only 10 years for its spectacular growth, but it can disappear even more quickly than it has grown. if Java continues along its current path, it will collapse under its own weight and become irrelevant in 5-10 years.
good move (Score:3, Insightful)
(http://vorlon.cwru.edu/~mlm11/projects)
--
http://unk1911.blogspot.com/ [blogspot.com]
at last! (Score:1)
I will finally be able to run Tomcat on my NetBSD/mac68k box without waiting for Kaffe to mature. Hooray!
Use Ada's model (Score:2)
Why now? (Score:1, Informative)
Fragmentation won't happen (Score:2)
Uh, am I missing something? (Score:2)
The goal is to get Java included in Linux distros (Score:2)
(http://www.osdev.org/)
Offical Sun JDK Distros Project [java.net]
Like a lot of people are already saying, you've been able to get the JDK source code for a long time now. The goal here is to fix the things that keep most Linux distro from including a JRE/JDK.
Bugfixes! (Score:2)
Well, we could always contribute them. But hopefully now they'll actually get applied.
The next OpenOffice.org will bundle its own Java (Score:2)
(http://cafepress.com/phototravel?pid=5934485)
I'm confident, it is only the Sun's restrictive licensing, that prevented them from bundling Java as well. Not any more...
Of course, you will still be able to use the already installed Java using the --with-system-java switch, but it will subtly break various things, because the OO.o's automated builds would never use it themselves.
It's all in the Money, Honey (Score:1)
The company is asking developers to provide feedback on how to best get there and prevent forking and fragmentation.
Well essentially, they want to stay in business - and don't want to give away code for free to competitiors. What if IBM/MS/any_other_company takes their code, repackages it and calls it "Their-Own-Kawa(TM)"? Their lead in the business as the premier Java would be lost.
I think they're thinking at it, purely from a business point of view. And it wouldn't help if the Chinese get a whiff of it (no offence intended).
More fragments (Score:1)
(http://192.168.1.2/tylerious/ | Last Journal: Tuesday December 07 2004, @11:41AM)
Re:Oh, dear lord (Score:1)
(http://www.creimer.ws/ | Last Journal: Friday January 26 2007, @12:40PM)
Huh? (Score:4, Insightful)
(Last Journal: Thursday November 11 2004, @12:40PM)
What else is *out there*? c,c++,C#, Visual Basic, Python? If your going to tell me its terrible, I certainly understand that point of view, please at least tell me what you cosider to be better and what applications you have in mind. Just telling me its bad and not good for much, doesn't help much.
Any suggustions to what is out ther that holds such great advantages to Java?
Re:Huh? (Score:5, Informative)
(http://www.intelligentblogger.com/ | Last Journal: Monday August 27, @11:47AM)
Patently false. [blogs.com] It has been false for years now. Ever since Chris Rijk published his earth shattering [aceshardware.com] benchmarks. (More recent benchmarks here [improve-technologies.com].)
It's now down to the skill of the programmer. A good programmer will write speedy code, and a bad programmer will write garbage. Who'da'thunk?
For another, its garbage collection has a tendency to result in really bad performance stalls
When was the last time you used Java? 1.1? The modern hotspot JVM uses a generational collector which should NEVER stall during runtime unless it begins running into memory pressure. Go try this game [javaunlimited.net] and tell us how many stalls you see. If you think that's too "simple", try this one [wurmonline.com].
For another, its portability has been hampered by not fully supporting interesting OS features, which means that there are all these OS-specific extensions to add things like audio support,
Is there something wrong with the javax.sound packages? I'm REALLY thinking that you haven't tried Java since 1.1.
They don't integrate well with other apps, don't do a good job of supporting OS services, etc.
Psst! [java.net]
Finally, Java makes it hard to add debug functionality into your code without a performance hit.
That's just a weak argument. Debugging info can really screw up a codebase and should be removed after debugging. But if you're wedded to the idea, get one of the three billion preprocessors [google.com] that are available.
The bottom line is that pretty much any compiled language has great advantages over Java.
The bottom line is that you haven't used Java since the days of 1.1, but you feel that you're fully qualified to make statements about a platform you know nothing about. Whether you intend to or not, you are trolling, sir. So I would ask you to stop spreading FUD by not commenting on Java until you are again familiar with the platform.
Re:Not such big news after all... (Score:2)
For instance, if one knows exactly how Java works, one should be able to make code intended for a Java VM compile into native binaries. That means that every Java app out there, and there are a lot, should be able to run much faster and in native windowing environments within Linux - and that Java code written natively for Linux would also be (somewhat) portable between platforms using VMs.
Again, I'm not a programmer, so someone correct me if I'm wrong.
Java is written in... (Score:1)
Really? Not in C/C++? How do you get the first compiler to run on a new architecture? Probably a cross-compiler.
(Not a troll: genuinely curious & ignorant)
Re:Get your forks ready.... (Score:2)
Re:Not such big news after all... (Score:3, Informative)
(http://www.mypalmike.com/)
For the bazillionth time, Javascript is not Java. I can't believe there are people on
Re:All true. (Score:2)
(http://www.mypalmike.com/)
While the following benchmarks are somewhat biased, they fairly reflect the speed of the previous generation of Sun's JVM. The latest one (5.0) improves upon this.
http://kano.net/javabench/ [kano.net]
Java's not the perfect tool for everything, but in my experience, it's great for making server applications that need to be reliable, maintainable, and fast, in that order. This is roughly the order in which many businesses need their software to be.
Re:All true. (Score:1, Informative)
You are delusional. Like or dislike the language, but it's had the fastest, strongest uptake of any language in the history of programming languages. It went from zero in 1994 to being almost neck-and-neck with C++ by 1998. In other words, it did in four years what C++ took nine to do, more if you amortize some of C's growth into C++'s history.
Popularity isn't everything, but don't try to say Java isn't popular. Do some searches on some job sites and see how many Java programmer jobs there are.
you get the slow startup times associated with JIT, and slow execution due to fiddling with bytecode. Let's not forget that the only type of optimisation carried out on the bytecode is peephole optimisation
Now you're just trolling. Slow startup time: sure. With the jdk 1.3, you had around an additional 700 ms. startup time penalty that you didn't have with C code; since then, it's gone down. These hundreds of milliseconds are enough to make Java a bad choice for a program like "ls" which gets run constantly, but is irrelevant for server use.
And the fact that little optimization is done on the bytecode ignores the huge amount of optimization that the hotspot compiler does; optimization that in some cases a statically optimized language like C++ cannot do.
Re:Get your forks ready.... (Score:2)
Eclipse is OK, but SWT is now a largely discredited waste of time.