News for hackers. Stuff that matters.
Re:Chrome now uses clang for production builds on Linux by mahouse on Monday November 17, 2014 @11:56AM (#8619043)
I'm sorry, but I don't understand. Aren't both Clang and LLVM open source?
Re:Chrome now uses clang for production builds on Linux by tedks on Monday November 17, 2014 @12:16PM (#8619167)
Not completely. Proprietary modules and forks of both exist, so in the broadest sense they are not (in the sense of, if I'm ever handed a copy of something calling itself LLVM, I do not know that it is libre software).

But worse than that, proprietary modules can be mixed-in to Clang and LLVM. So essential functionality can be hidden in proprietary modules. Imagine that Apple wants to do something nifty for Swift, but doesn't want Google to be able to use it in Go -- they'll release a proprietary module that can be linked into Clang.

All free code in LLVM can be forked and made proprietary, and no proprietary code can be reasonably expected to be liberated. So the balance of free to non-free code can only ever get worse.

I'm sure that the libre software world being based on a proprietary compile will be a great thing to add into the mix of pervasive surveillance and network penetration.

Re:Chrome now uses clang for production builds on Linux by danieldk on Monday November 17, 2014 @12:23PM (#8619209)
Not completely. Proprietary modules and forks of both exist, so in the broadest sense they are not (in the sense of, if I'm ever handed a copy of something calling itself LLVM, I do not know that it is libre software).

By your definition, any non-copyleft open source licensed software ceases to be open source 'in the broadest sense' once a proprietary fork exists. Which is just silly, some software is open source according to the open source definition or it is not.

Imagine that Apple wants to do something nifty for Swift, but doesn't want Google to be able to use it in Go -- they'll release a proprietary module that can be linked into Clang.

People who pick the Apache, MIT, or any non-copyleft open source license do this knowing that proprietary forks or extensions are possible. Not everyone's definition of 'freedom' is the same as the FSF.

Also, I would like to point out that the same thing happens in copyleft-land. Companies dual-license their code under a proprietary license and let contributors sign agreements, to shut out competitors and to get people to buy expensive proprietary licenses. Oracle thankfully uses the GPL for such strategies. In fact, they recently relicensed Berkeley DB and Berkeley DB XML under the AGPL(!).

I'm sure that the libre software world being based on a proprietary compile will be a great thing to add into the mix of pervasive surveillance and network penetration.

Just help me understand. FreeBSD takes the open source LLVM/clang, uses it to compile their open source software. And suddenly it becomes proprietary. How so?

Re:Chrome now uses clang for production builds on Linux by anon1385 on Monday November 17, 2014 @01:05PM (#8619446)
>Not completely. Proprietary modules and forks of both exist, so in the broadest sense they are not

This is also true of GCC. Lots of organisations have private forks and the GPL allows that. More generally, if somebody offers 'compiler as a service' over the internet then the GPL becomes irrelevant and they could add as much private code to GCC as they wanted. The GPL only forces you to contribute back under a very specific and narrow set of criteria. Criteria that the majority of software being written in 2014 doesn't meet. The GPL is largely irrelevant to most software shops these days - they freely incorporate piles of GPL licensed code into proprietary closed source products. They can do so because most new software is internal to organisations or delivered as an internet service. The GPL was designed for a different world.

Software freedom has been set back because of people clinging to the GPL as the final word in software freedom. Your kind of GPL centric propaganda results in young developers today thinking they are doing the world a favour by writing proprietary closed source web apps - because they are using FOSS GPL libraries, right? And targeting the 'open' web, right?

Do you AGPL licence all the code you write, including website backends? Does your employer? If not you should probably take a close look at yourself and consider that maybe you are part of the 'problem' you are decrying.

Re:Chrome now uses clang for production builds on Linux by tobylane on Monday November 17, 2014 @12:36PM (#8619275)
Someone who owns and distributes GPL-licenced software is not bound by the licence, they can allow themselves to fork it with a different licence. Apple employs the owner of CUPS, so they could abandon cups and 'start' anew closed-source.
Re:Chrome now uses clang for production builds on Linux by GrinningFool on Monday November 17, 2014 @01:27PM (#8619604)
" So the balance of free to non-free code can only ever get worse"

This would be true if people could not and did not write new free LLVM code/modules...

Re:Chrome now uses clang for production builds on Linux by DannyBee on Monday November 17, 2014 @05:03PM (#8620954)
"Not completely. Proprietary modules and forks of both exist, so in the broadest sense they are not (in the sense of, if I'm ever handed a copy of something calling itself LLVM, I do not know that it is libre software)."

Proprietary forks and modules of GCC exist too. Shocking, I know.

Re:Chrome now uses clang for production builds on Linux by tedks on Monday November 17, 2014 @11:53PM (#8622425)
Well, if they do they're never distributed, so a better term would be private, not proprietary.

I suppose in the corporate sense, these two things are indistinguishable, so I should specify that I meant non-free, in the free-as-in-freedom sense, but I don't think I was ambiguous.

I've been having this conversation in good faith, though my opinion is unpopular, and I'd invite you to do the same.

Re:Chrome now uses clang for production builds on Linux by chimeracoder on Monday November 17, 2014 @12:01PM (#8619070)
OP is being a rather hyperbolic, but it's not really that unreasonable to criticize Clang/LLVM on this issue.

Both projects are politically motivated. GCC began explicitly as a project to provide a FOSS C compiler (few if any existed at the time). Clang/LLVM didn't start at Apple, but their development has been heavily sponsored by Apple, whose interest in the project stems from their interest in excising the GPL (and specifically the GPLv3) from their entire development stack. (Notice how the version of bash that ships with OS X is almost a decade old, and is also the last version that was released under GPLv2).

The fact that Clang/LLVM are released under a FOSS license today does not mean (A) that they always will be, or (B) all essential functionality will always be[0]. With GCC, being a FOSS compiler collection is their entire raison d'etre - it's right in the name![1]

Edit: Reworded sentence to remove ambiguous antecedent.

[0] (ie, it's conceivable in the future that nobody will want to use Clang/GCC on its own, but will essentially have to use it in conjunction with another piece of related software, and there's no guarantee that this software will be FOSS. With GCC this is not a relevant concern only because the FSF would never let that happen; it undermines the entire founding point of the project.

[1] GNU Compiler Collection

Re:Chrome now uses clang for production builds on Linux by CJefferson on Monday November 17, 2014 @12:07PM (#8619109)
To be fair to clang, one big motivating reason for starting clang (one of the reasons I got involved in helping clang myself) was the fact that at that time GCC would refuse any patch which made it easier for anyone to get a C++ parse tree out of gcc.

clang was designed to do that from the start, and for me this has lead to greatly improved C++ tools.

Re:Chrome now uses clang for production builds on Linux by pnathan on Monday November 17, 2014 @12:41PM (#8619303)
> To be fair to clang, one big motivating reason for starting clang (one of the reasons I got involved in helping clang myself) was the fact that at that time GCC would refuse any patch which made it easier for anyone to get a C++ parse tree out of gcc.

A friend of mine is a long-time kibitzer of C compilers, and his occasional remarks about the state of the world wholly harmonize with this - GCC was not good for interop, and the contributing process has a higher bar than others.

Re:Chrome now uses clang for production builds on Linux by DrJokepu on Monday November 17, 2014 @12:06PM (#8619103)
Actually, the reason Apple sponsored Clang/LLVM is because Apple engineers were unhappy with GCC's build times[1]. If you need to rebuild an entire operating system (kernel and userland) every day, your C compiler's build performance matters a lot.

[1] http://www.imore.com/debug-48-melton-ganatra-episode-ii-unde...

Re:Chrome now uses clang for production builds on Linux by jakobegger on Monday November 17, 2014 @01:25PM (#8619590)
A major problem with the GPL from the point of view of a closed source software vendor is that you can't integrate it into a closed source project.

Apple wanted to integrate the compiler more deeply into their IDE, Xcode. GCC didn't allow that without making Xcode GPL too - which was out of the question. Apple has no problems contributing changes back to GCC or clang -- but there is no way they will make XCode open source.

Clang allowed Apple to take their IDE to a whole new level. Since the move to clang, features like code completion, scope higlighting, refactoring tools and inline error display (with somewhat helpful autocorrect suggestions) have vastly improved.

Apple didn't want to get rid of GCC out of spite, butthe restrictions of the GPL were holding them back. If you are a supporter of copyleft licenses, you'll see this as a success (hindering proprietory software), but from Apple's perspective it is obvious why they chose to support a compiler with a more liberal license.

Re:Chrome now uses clang for production builds on Linux by rsynnott on Monday November 17, 2014 @01:48PM (#8619718)
> A major problem with the GPL from the point of view of a closed source software vendor is that you can't integrate it into a closed source project.

And a major problem with GCC related to the GPL is that it has historically resisted changes which would make it easier to integrate even into an open-source project, though it has eased up on this a bit lately (possibly due to competition from clang?) Still, there's a reason that code completion and other code-aware plugins for things like vim and emacs are increasingly clang-based.

Re:Chrome now uses clang for production builds on Linux by adekok on Monday November 17, 2014 @03:58PM (#8620512)
> A major problem with the GPL from the point of view of a closed source software vendor is that you can't integrate it into a closed source project.

Commercial software usually has the same problem. Those dang companies won't give me their source for free, and they demand a license fee to integrate their products into mine!

The issue with the GPL is less the GPL than the multitude of authors for any one project. There are many single-author GPL projects which happily accept money for a non-GPL version of the software.

That becomes much harder when you have 40 authors, some of whom are dead..

Re:Chrome now uses clang for production builds on Linux by DannyBee on Monday November 17, 2014 @05:06PM (#8620974)
"but their development has been heavily sponsored by Apple, whose interest in the project stems from their interest in excising the GPL (and specifically the GPLv3) from their entire development stack."

This is not accurate in any respect. It would be accurate if you said "early development" (original development was sponsored by UIUC).

Their interest in the project was not at all in excising the GPL. They didn't care. That was a political position they took once on a GCC mailing list. But lawyers do not run Apple. If they wanted to keep using GCC, they would have kept using GCC.

They wanted faster build times, a better infrastructure, and something they felt they could invest in and not have this amazing uncertainty about where it was going and what it's goals were. They also didn't want to have engineering stymied by the politics of GCC (it is less political now, it was very political then).

Re:Chrome now uses clang for production builds on Linux by mikepurvis on Monday November 17, 2014 @12:10PM (#8619130)
The "piece of related software" is likely to be a binary blob that outputs the special instructions for some optimization in a new CPU, or GPU instructions, or similar.

Or it could be a frontend for a new proprietary language.

Or a backend for a whole new architecture.

Re:Chrome now uses clang for production builds on Linux by justincormack on Monday November 17, 2014 @12:47PM (#8619337)
They already exist, particularly for GPUs. We know that there are few open GPUs and gcc being GPL is not going to open them.
Re:Chrome now uses clang for production builds on Linux by rsynnott on Monday November 17, 2014 @01:45PM (#8619707)
In practice, Apple's hardly the only contributor to LLVM these days, though; Google's on the same scale, and there are other large contributors. If Apple or Google or another large contributor stop contributing, it's likely that those remaining will fork if necessary and continue.
Re:Chrome now uses clang for production builds on Linux by VikingCoder on Monday November 17, 2014 @01:44PM (#8619697)
> The fact that Clang/LLVM are released under a FOSS license today does not mean (A) that they always will be

The versions of Clang and LLVM that you have today will ALWAYS be available under the license they're currently under.

You're fear-mongering that the current contributors of Clang and LLVM may, in the future, make new releases under licenses you don't like.

But if people like Clang and LLVM, they can fork the current code, and keep adding features to it under a compatible FOSS license.

Re:Chrome now uses clang for production builds on Linux by Nursie on Monday November 17, 2014 @01:55PM (#8619767)
>> The versions of Clang and LLVM that you have today will ALWAYS be available under the license they're currently under.

This is a bold claim! Are you providing the hosting?