Recommendation: no GPLv3 for Solaris [LWN.net]

Recommendation: no GPLv3 for Solaris

Posted Feb 11, 2007 7:50 UTC (Sun) by drag (subscriber, #31333)
In reply to: Recommendation: no GPLv3 for Solaris by Arker
Parent article: Recommendation: no GPLv3 for Solaris

One thing to keep in mind also is that the OpenSolaris folks obviously don't have a problem with the CDDL otherwise they wouldn't be OpenSolaris developers.

So since they have no problem with the CDDl then why would they care about GPLv3?!

It's like asking a dedicated Java developers if they have a problem with Java being propriatory or asking X.org developers if they would want to go GPLv3.

I can pretty much garrentee what sort of response you'd get. It doesn't nessiccarially mean thats what is (or not) the best thing for Sun or Solaris itself though.

Linux is nailing Solaris to the wall in terms of market performance and without GNU it wouldn't be possible.

Gaining built in GNU support and licensing compatability with those developers who currently favor Linux over Solaris is going to provide the best way to move Solaris/OpenSolaris forward. It's just make sense.

(Log in to post comments)

Proprietary Java

Posted Feb 11, 2007 10:00 UTC (Sun) by man_ls (subscriber, #15091) [Link]

Yeah, true. I used to troll in a Spanish Java forum; to annoy people there all you had to do was to ask Sun to free their implementation, and then they all repeated like parrots that it had no advantages, that it did not matter to anyone, that Microsoft would make incompatible versions, that the sky would fall upon their heads if they did.

Now, when Sun announced they were going to release Java 7 under the GPL most of them were just astonished and didn't say anything; the rest congratulated Sun on having such a great vision and generosity and warm hearts. It was amazing to watch!

Most people don't care for consistency, they just want a cozy environment. Sad but understandable.

Recommendation: no GPLv3 for Solaris

Posted Feb 11, 2007 17:09 UTC (Sun) by mrshiny (subscriber, #4266) [Link]

I think it's funny that you totally discount the possibility that a user of a system might want it to be open. As a professional java developer, I am thrilled that it will be opened, because this will result in many improvements, including support for under-supported platforms and support for unusual configurations. For example, Sun didn't ship a 64-bit applet plugin for Linux; this is because of the variety of issues with shipping a compiled 64-bit blog to plug into a browser; the problem isn't that hard but Sun didn't want to deal with it. Now that Java is open, this issue will finally be resolved, and similar issues will also be resolved. Also users will finally be able to fix bugs in a more timely manner than Sun. And finally, for embedded developers, there are a range of possibilities when you have the freedom to alter the core platform in a way that suits you.

I mean, you can't say that, just because someone tolerates the status quo, doesn't mean they don't want it to change.

Recommendation: no GPLv3 for Solaris

Posted Feb 12, 2007 0:37 UTC (Mon) by drag (subscriber, #31333) [Link]

""I mean, you can't say that, just because someone tolerates the status quo, doesn't mean they don't want it to change.""

That's right.

But when somebody _chooses_ to join that statis quo, then that is different. It's one thing to get sucked into it, but it's quite another when somebody volenteers for it.

If they had problems with licensing of OpenSolaris then they would be Linux developers, not OpenSolaris developers. :-)

Plus another thing is that CDDL is a Free software license, by FSF/RMS's definition of the word. The question is one of licensing incompatability, not of freedom on the GPLv3 side (OpenSolaris folks probably like that CDDL allows them to use the code in propriatory software, were the GPLv3 would not)

Recommendation: no GPLv3 for Solaris

Posted Feb 12, 2007 15:55 UTC (Mon) by Arker (guest, #14205) [Link]

I don't think the point was that developers in general don't want that, it was that the developers working at any given time on a given project are likely to be the ones that don't have a problem with the license that project is under.