Sun To Choose GPL For Open-Sourcing Java 407
An anonymous reader writes, "Sun is about to announce its plans for open-sourcing Java SE and ME, according to CRN — and they're going to use the GPL, not their own CDDL or another less-restrictive license."
w00t! (Score:2, Insightful)
Re:w00t! (Score:5, Insightful)
No, wait, it's Slashdot!
Re:w00t! (Score:4, Funny)
Re:w00t! (Score:4, Insightful)
Re:w00t! (Score:4, Funny)
Yeah, I'd noticed that. Also, almost every article about MS is tagged fud, notfud, itsatrap and notatrap, most of the political articles are tagged fud and notfud. Nice to see I'm not the only one getting annoyed that people seem to be using tags as comments. Mind you, is it really surprising?
yes, no, maybe
Re: (Score:2)
Re:w00t! (Score:5, Interesting)
Re:w00t! (Score:5, Funny)
You grossly misunderstand. (Score:5, Insightful)
A static VM obtained from Sun will not require source distribution when included in your product, since Sun maintains that. So anyone using Java now won't notice the difference.
It's open source, and there's no way it can be used AS THE BASIS of a 3rd-party product that isn't open source without Sun's permission, which is how they want it.
Who loses? If you want sole modification/closed distribution rights, you can get a source license directly from Sun, just like you do right now.
Yesssssss........ (Score:5, Funny)
Re: (Score:2)
Re:Yesssssss........ (Score:4, Insightful)
Re: (Score:2)
Re:Yesssssss........ (Score:4, Insightful)
Microsoft's VM was a lot better than Sun's at that time, and their Windows GUI library made AWT look like the utter pile of shit that it was. They also put a lot of effort into marketing Java as the future of Windows application development to developers, and had a language independent native interface and interoperability layer that was offered to Sun, but rejected in favour of JNI.
"Sun decided that pure Java was more important than success on the Windows desktop so I guess they should be happy that things turned out the way they wanted."
I think it was more of a case of Scott McNeally's pathological hatred of MS leading to yet another in a remarkable series of bone-headed maneuvers that ended up nearly bankrupting Sun. This particular bone of contention seemed to revolve around the fact that while the MS VM and libraries supported JNI, their use required a command-line switch, and Sun reckoned that the command-line switch should be used to enable Microsoft's options rather than theirs (for some reason, an old illustration of Swift's Lilliputians and their war over what end of a boiled egg was the correct one for breaking with a spoon kept coming to me whenever I read about that particular saga).
"These days MS isn't interested in Java and Windows developers are even less interested."
And because of Mono, the same can be said for growing numbers of Linux and OS X developers. By cutting off their own nose to spite their face, Sun not only closed the door on a big source of revenue (MS were their biggest, and therefore most lucrative licensee at that time), but also spurred the development of a competing system by a company with effectively unlimited funds that had already written their own Java compiler, VM, and libraries, and therefore had a very good idea of not only what Java had done right, but also what was wrong with it. This together with Sun's foot-dragging over open sourcing Java led in its turn to a clone of the competing system that check-mates Java's ability to run on a variety of platforms. Way to go Sun!
Re:Yesssssss........ (Score:5, Insightful)
Given Sun and Microsoft's past history I would imagine sun would test anything that came out of Redmond wanting to be called "Java" very carefully.
Re:Yesssssss........ (Score:5, Insightful)
True... MS would have to call it something else... like... say... J++? Or maybe J#?
If the MS-Novell deal turns out to be the catastrophe that everyone thinks it is (based on MS' track record of how it treats its "partners"), then this is a really smart move for Sun. SuSe and Gnome get tainted, Mono becomes a dirty disease, what's left to fill in the void? Java: the reason why .NET and Mono exist in the first place.
Re: (Score:3, Funny)
So shortly after they release it under the GPL, we can expect to see "Gnuzilla IceKona".
Re: (Score:2)
Re: (Score:3, Interesting)
Let someone clarify... (Score:5, Insightful)
Re:Let someone clarify... (Score:5, Informative)
Re:Let someone clarify... (Score:5, Insightful)
It also affects all the regular users of ready-made distributions who only package and distribute GPL software.
Re: (Score:2)
Re: (Score:2)
I imagine it will affect fewer people than that. If Sun retains the copyrights to the code and existing licensees do not wish to publish their source code under GPL, Sun can continue to license the source code to them under different terms for a fee. For those licensees, the arrangement wouldn't be any different to how it is now.
This is very much a good thing for Sun.
Matlab (Score:2)
How does GPL'ing the Sun libraries... (Score:2)
I mean, doesn't that just cover sun.* and java.*?
Re: (Score:2)
considering that the GPL is a distribution license and not a use license, i fail to see how it would have any effect at all on linking with non-GPL code by an
Er... (Score:5, Insightful)
I mean, I know some people have a mad on against the GPL, but it ain't what you'd call restrictive. The only thing it does is mandate that all derivitve works also have to be GPLed.
Re:Er... (Score:5, Insightful)
Out of the most popular Free licenses, GPL probably is the most restrictive - many others don't have the restriction you mention.
Not to say that I don't think the GPL is a good choice for this.
Re: (Score:3, Informative)
The GPL really only has one restriction worthy of the name: that software placed under the GPL must remain free, in accordance with the wishes of the programmer who first placed the software under the GPL. It is precisely this alignment with programmer's wishes that makes GPL so popular.
Re:Er... (Score:5, Insightful)
The freedom the GPL is taking away is for someone to take source code that is GPL'd and then:
1) Take that code, bundle it into a restrictive (often commerical) license and give nothing back to the community
2) Put it into a BSD style or public domain which is fine - until somebody does 1)
Re:Er... (Score:5, Insightful)
Re: (Score:3, Insightful)
Just because the GPL isn't terribly restrictive doesn't mean there aren't alternatives that are less restrictive. The BSD license comes to mind.
Re: (Score:2)
Re:Er... (Score:5, Insightful)
It lacks the assurance that your software will remain Free and open source to anyone who uses it. This is something you can do with GPL'd code that you cannot with BSD'd code; make a legal guarantee about the freedom of the software.
Which is more free?
1) that which ensures freedom or
2) that which grants so much freedom that it permits denial of freedom
You make the argument that the answer is obvious, but if you pause to think rather than simply mashing the "reply" button, you may find that it is actually a question worthy of some consideration. I'm not saying I know the answer, but the answer has far reaching ramifications many arenas (abortion, wars, government, software, etc.)
Re: (Score:2)
Maybe you want to re-read the post you're replying to. The fact that BSD is more permissive is precisely the reason why Sun opted for the GPL.
Re: (Score:2)
That makes the GPL one of the most restrictive "open source" licenses out there. MIT, Apache, BSD, and others do not have this restriction, allowing that code to be incorporated into non-GPLed works.
Re: (Score:2)
Lesson of Trolltech (Score:2)
Re: (Score:2)
Re: (Score:3, Informative)
On the one hand, you could say that the people
And in other news tonight: (Score:5, Funny)
I'll believe this when I see it.
Will this lead to better desktop Java? (Score:4, Insightful)
On the other hand, is this Sun's way of wiping their hands clean of everything besides their only Java moneymaker (J2EE)? They must realize that desktop Java has seen its day, and this might be a way to save some development resources while they continue to restructure in light of recurring market share losses.
Re: (Score:2)
Re: (Score:2)
And this is the thing that blows me away to this day. I don't know how many good-sized projects I've seen[1] (e.g., division-wide CRM) that get originally proposed for .NET implementation, only to founder when someone points to the hardware requirements and says "I have to buy $50K worth of new Windows servers? Why can't we run it on the Oracle server? That thing's huge and cost us a mint." Said Oracle server (naturally) running on either HP-UX, Solaris
Re: (Score:2)
Re: (Score:2)
Sounds like you should have gone with SQL Server instead of Oracle. You'd have saved a mint. Then you could have hung Microsoft Dynamics off your SQL Server database and
Re:Will this lead to better desktop Java? (Score:5, Insightful)
Not obvious at all (Score:4, Insightful)
Re: (Score:2)
Correction: Not the only moneymaker (Score:3, Informative)
Actually, J2ME is a primary Java moneymaker for Sun, also. I work for an enterprise IT weekly (InfoWorld) and my colleagues and I always end up rolling our eyes whenever we are invited for a big press chat at Sun only to be regaled for half an hour with stories about running games on Java-powered cell phones. We could care less about games, but it's obviously a big issue for Sun and
This is a great move...even for the anti-GPL (Score:5, Insightful)
When you look at the other Java implementations, you have the Apache-licensed Harmony, and commercial implementations from IBM and BEA.
Java can only be helped by this because it removes one of the major objections Linux backers have against using Java.
Thats not what its about (Score:3, Insightful)
IBM Java is going away.
Re: (Score:2)
Hey, then everybody is in agreement because MS doesn't want any of Java's VM technology in
Doesn't make sense (not just grinding an axe) (Score:2)
This won't be embedded in a lot of things because of that. It seems like LGPL makes more sense for this, since Java is often embedded in other apps. Firefox isn't GPL. Can they mix and match without changing the license? Maybe, maybe not; LGPL would have made the question unambiguous.
Re: (Score:2)
Re: (Score:3, Informative)
Just like Linux isn't embedded in a lot of things?
Keep in mind that proprietary Java programs may be developed and run under a GPL'd Java system.
Re: (Score:3, Informative)
Yes, it is. Firefox is tri-licensed under MPL, GPL, and LGPL.
This is great (Score:5, Insightful)
For those who have already started complaining about the license in this thread - why don't you spend a few years writing your own Java clone, and giving it away under BSD or whatever?
Are they going to pull a "sun4m stunt" with Java? (Score:2)
Pieces will be missing (Score:2)
Re:Are they going to pull a "sun4m stunt" with Jav (Score:2)
Interesting, if true (Score:5, Insightful)
Second remark - I think the GPL is a good choice for this. Consider what Sun might gain from open source Java under any license:
1) Excellent integration with Linux, *BSD, and any other platform out there they haven't integrated into fully yet (except maybe Windows). They would get all the work done for free, too - distributions would be chomping at the bit to work long and hard on making everything work Just So.
2) Much better realization of cross platform "write once, run everywhere" goals. Well integrated Java everywhere can only help this.
3) Possible improvements as people get a chance to fix anything that's been annoying them for the last several years.
All very logical reasons to open source, IMHO - Java is already freely downloadable. Sun owns the Java trademark, so they have no fear of forks which mean anything in terms of threatening Java mind share - Java has to be one of the most publicly recognizable programming language brand names in the world. Sun will always provide the "only" Java, whatever else out there might run Java programs.
Now, what does GPL do for them, that other licenses might not?
1) Credibility - rather than inventing Yet Another License, making things simple using already established (and I think functional for this purpose) licenses.
2) Prevents commercial forking. Whatever open source Java becomes, it is unlikely that someone would try and compete commercially against Sun when Sun has the commercial code base and original developers. Any work any commercial developer did in competition (that they want to distribute anyway) would have to be offered free to the world under GPL, and even if Sun can't use it directly the ideas alone would be enough to allow them to keep up and maybe get there first in some cases.
3) Allows maximal code sharing in the open world. GPL has its own momentum, as a sort of "logical end point" - free except for the ability to become non-free. That would seem to make a lot of sense to me for Java, particularly since I would expect (like OpenOffice) that most of the best code would come out of Sun and be copyright Sun. Sun can put out what it wants, and still license commercially if they so choose.
Downsides for Sun primarily seem to be the "radical" image associated with GPL in some circles (yes that's a disadvantage if you want to look like a reasonable, sane business to some PHBs) and the inability to combine developments based on GPL Java back into their commercial Java without discussing it with the author. But since this very restriction is also a reassurance to the community in some ways, it might not be all bad.
Anyway, I will watch developments with interest and look forward hopefully to the day when Java on Gentoo can be well integrated and smooth.
Re: (Score:2)
Re: (Score:2)
You cannot GPL Java, if you do, then ***ALL*** the business applications
that are created using Java will have to ***PAY*** a license fee to use it.
PERIOD.
---
Put the crack pipe down and go back and read the fucking license. You're full of shit and there's a danger that some of the more gullible slashdotters might believe you.
L
Re: (Score:2)
Why is it bad? It's the same as any other commercial software like, say... microsoft windows... you start using it and then you are locked in and have to pay taxes to the software company for the rest of time. If you open up and GPL all your software (instead of locking it down) you can then sell support for your product, you never pay fees... I think its that people like you are scared of having to do some support work and would rather write once and live off profit
J2SE then J2EE and Glasfish to follow (Score:2)
The complete package is almost - if not - on the same level as projects like GCC and GNOME.
Not to mention, it is very exciting to consider what this new truly democratic "Java Community Pro
This is such awesome news for all of us... (Score:3, Insightful)
Sun was making some missteps... for instance how badly EJB sucked up to 2.1.
Now we have POJO's implementing enterprise beans in 3.0. We have strong standardized support for security and cryptography (ala JCA/JCE, JSSE, JAAS). JDBC is a snap. We have excellent documentation and books available from J2ME to J2EE....
Between Britney Spears being available again and the Repubs losing House and Senate... I'd say it was a good day.
New License (Score:3, Insightful)
They have no qualms of people seeing the code, submitting code, compiling on their own, etc? They want to port to all systems, etc.
There seems to be a huge void here. We need a license that covers this scenario and specifically prevents unauthorized forks. Change the code on your own machine. Submit upstream if you wish, but you can't distribute unofficial builds, or fork the code.
If such a license existed, it might be considerably more likely to see more open-source codecs, open sourced Flash players, plugins, video drivers, etc.
Sun has said forever that the code is basically out there already, and they had no qualm making it open-sourced over than the fork issue, and the only reason for this lengthy delay was coming up with an appropriate license. So why just settle on the GPL?
I'm confused.
Re: (Score:2)
Sun still owns the Java trademark. If you try to fork Java, then their lawyers will say to you, either you stop calling your fork 'Java' or we sue you for trademark infringement. They don't need to actively prevent people from making forks in this case. Besides, a license of the kind you describe would neither qualify as a Free Software license by the FSF's definition nor an Open Source license by the OSI's definition. Besides, historically, forks of major projects are extremely rare, and are most commo
Re: (Score:2)
And I've never once heard Sun talk about open-sourcing without mentioning their fear of forking.
Forking is an essential right (Score:5, Insightful)
Re: (Score:3, Interesting)
Inkscape (nee Sodipodi) is another one.
How will this affect code written in Java? (Score:2)
Re: (Score:2)
What exactly are they open sourcing? (Score:2)
If its just the virtual machine and not the libraries, its less usefull (since the libraries would remain non free)
Um set to move? (Score:2)
Oh, heck. (Score:2)
What happens to GCJ and Fedora now?, I wonder.
This will be super cool. (Score:4, Interesting)
Better; part of your browser that _cannot_ be integrated into non-GPL browsers. They still have to run it as a plugin.
This has mind-boggling implications in terms of patents that apply only to browser plugins (ahem---Eolas).
I've always wished for a Firefox with Java + Flash integrated (does that even make sense?). I don't feel that plugins give as good of an experience as native browser controls.
Re: (Score:3, Informative)
Technically, the difference should be zero, else something is very wrong. Take Safari/Konqueror for instance; *everything* is handled by plugins, right down to simple images.
Plugins really are just elements like anything else, they are just loaded at run-time and not linked statically into the browser. Thats all.
Too bad it's too late (Score:2)
Re:Too bad it's too late (Score:4, Interesting)
Re: (Score:3, Interesting)
GNU (Score:2, Interesting)
Did you actually read the article? (Score:2, Interesting)
Hrmm.... (Score:2)
Huge impact on free operating systems (Score:4, Insightful)
If Sun releases both the Java VM, and (more importantly) the Java class libraries under the GPL, it will be huge, because important packages will now be able to include Java functionality out of the box
Example: Distros can ship Firefox (a.k.a. Iceweasel/Firesomething/whatever) with a Java plugin. On every architecture. Running OpenBSD. And it'll be reliable, because weird OS-specific bugs will actually get fixed.
Another example: Debian et al. can start shipping OpenOffice with Java support.
If Sun plays its cards right, it will have eliminated the so-called Java trap [gnu.org], which can only serve to render Java more ubiquitous.
That said, I'll believe it when it happens.
GPL2 or 3? (Score:5, Interesting)
Re: (Score:3, Insightful)
Re: (Score:3, Insightful)
Re: (Score:3, Informative)
Any ARM chip with a J in its name incorporates Jazelle, which allows it to run Java bytecode natively. Other chips support Thumb-2EE mode, which does things like null pointer and array bound checking in hardware, and is designed as a target that it is easy to JIT compile Java bytecode to.
Any modern 'phone has a J2ME runtime environment, often accelerated by using one of these features. Last week Erisson released their J2ME stack under the Apache 2.0 license.
Re: (Score:3, Interesting)
Amazing you guys say this now. Yesterday someone would have argued java is clean and fa
Re: (Score:3, Insightful)
You shouldn't confuse the author of the parent post with the Java crowd in general. You used the term "you guys" (referr
Another very large fork (Score:2)
It is not unprecidented, if someone had good reason to do so. However I don't think it would happen because pressure enough to seek a fork of that size would at least try to work through the JCP [jcp.org] java standards body to add what they were seeking. And many things people would like to do with Jaqva can be done as libraries, fewer things need to modify the language itself or the bytecode structure.
Re: (Score:2)
Forget that man! (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:3, Interesting)
For those of you not familiar with it, Java goes hunting for all code at runtime based on the fully qualified (package + class) class name, and resolves methods and fields based on name as well... the code that gets executed at runtime can be completely different than the code compiled agai
Re: (Score:2)
I don't have to go tell Sun's CEO anything... if they GPL Java they will kill it. Period.
Therefore, I am forced to conclude that either the article is not entirely correct and Sun will actually be using a licensing policy _SIMILAR_ to the GPL (maybe the LGPL), or else Sun is incompetent. I am equally prepared to believe either.