LLVM & GCC Compiler Developers To Begin Collaborating 279
An anonymous reader writes "While RMS is opposed to LLVM over its BSD-like license rather than the GPL, LLVM/Clang and GCC developers have agreed to try to start cooperating in an "open compiler initiative" to jointly tackle common issues that plague both compilers and issues that can be better served by working together rather than creating fragmentation between the two popular open-source compilers."
Re:Open borders... one way? (Score:5, Informative)
I'm pretty sure this is not about sharing code, but about collaborating on needed features via a shared spec. So both compilers implement something a standard way instead of coming up with new features independently.
BETA & WINDOWS 8 Developers To Begin Collabora (Score:1, Informative)
Please post this to new articles if it hasn't been posted yet. (Copy-paste the html from here [pastebin.com] so links don't get mangled!)
On February 5, 2014, Slashdot announced through a javascript popup that they are starting to "move in to" the new Slashdot Beta design. Slashdot Beta is a trend-following attempt to give Slashdot a fresh look, an approach that has led to less space for text and an abandonment of the traditional Slashdot look. Much worse than that, Slashdot Beta fundamentally breaks the classic Slashdot discussion and moderation system.
If you haven't seen Slashdot Beta already, open this [slashdot.org] in a new tab. After seeing that, click here [slashdot.org] to return to classic Slashdot.
We should boycott stories and only discuss the abomination that is Slashdot Beta until Dice abandons the project.
We should boycott slashdot entirely during the week of Feb 10 to Feb 17 as part of the wider slashcott [slashdot.org]
Moderators - only spend mod points on comments that discuss Beta
Commentors - only discuss Beta
http://slashdot.org/recent [slashdot.org] - Vote up the Fuck Beta stories
Keep this up for a few days and we may finally get the PHBs attention.
-----=====##### LINKS #####=====-----
Discussion of Beta: http://slashdot.org/firehose.pl?op=view&id=56395415 [slashdot.org]
Discussion of where to go if Beta goes live: http://slashdot.org/firehose.pl?op=view&type=submission&id=3321441 [slashdot.org]
Alternative Slashdot: http://altslashdot.org [altslashdot.org] (thanks Okian Warrior (537106) [slashdot.org])
Re:RMS needs to get over the GPL (Score:5, Informative)
Actually, no. You may use GPL'd code any way you like (that's freedom 0) and share with others (freedom 2). You can likewise modify the software any way you like (freedom 1). And all this time, you need not release source code. The condition to release the source only kicks in with freedom to distribute your changes (freedom 3), so only when there is a third person involved with your derivative you have to grant them the same freedoms you've been given by the original author.
In fact, this was a problem with SaaS: You could've modified free software, and run it in the back on your servers, and say that you're simply providing a service to the end user, and since he's not getting the modified program, he doesn't get to have its source either. This is what AGPL is designed to address, and thus it's mostly used for web software. So with AGPL, as soon as you use a program, whether you have a copy, or are executing it online, you get access to the source.
Re:RMS needs to get over the GPL (Score:4, Informative)
Neither the BSD nor the GPL remove (not can they remove) the aspect that copyright requires that a person must get permission from the original copyright holder if they are creating a derivative work of something copyrighted. In that light, both the BSD and GPL licenses essentially state that everyone who adheres to the terms of the license is free to create derivative works, thereby effectively granting such permission... but still only to people who adhere to the terms of the license.
Of course, the terms of the BSD license are pretty lax in comparison to the GPL... the former being not much beyond keeping the copyright notices in header files intact, while the latter license requires that the derivative work be released under the same license.
Re:The GPL is like the Slashdot Beta: Unwanted! (Score:4, Informative)
First off the author always has the freedom to do whatever they want (assuming they haven't transferred copyright to someone else), the license only applies to *other* people. If you're the author of a derivative work and feel you should get to claim credit for the whole of "your" work, then by all means feel free to replicate the no doubt trivial amount of labor put into all those libraries you used.
BSD grants essentially unlimited freedom to developers directly downstream, but makes no attempt to preserve those freedoms for anyone further downstream.
GPL grants somewhat restricted freedoms to downstream developers, but in doing so they ensure that everyone further downstream continues to get the same freedoms.