News for hackers. Stuff that matters.
Re:Chrome now uses clang for production builds on Linux by TallGuyShort on Monday November 17, 2014 @12:25PM (#8619219)
Remember that time that Apache destroyed software freedom because it wasn't GPL? Me neither.
Re:Chrome now uses clang for production builds on Linux by idontknow12 on Monday November 17, 2014 @12:44PM (#8619316)
If you have a competitive advantage why contribute back in any meaningful way? We have seen this type of stuff on Android with Dalvik (where Qualcomm has a special library / modified version of the VM).

That's not to say it destroys freedom, but its not ideal for a certain subset of software. The GPL is also not magical in this regard, since you have projects where things don't get up streamed.

Re:Chrome now uses clang for production builds on Linux by protomyth on Monday November 17, 2014 @01:19PM (#8619540)
> If you have a competitive advantage why contribute back in any meaningful way?

Cost. If your advantage was perpetual and didn't increase your future support costs, then sure, you wouldn't contribute it back (ignoring belief / culture).

It isn't though. Someone will do something similar and even if they don't, each new version requires you to not upgrade or spend the time integrating your wonder code into the mainline again.

Long term cost of staying current is going to be an issue. Each change to your fork makes bringing in new features from the original harder.

Plus, in my mind, it is a nice self selected pre-screening filter for companies / individuals that would be good to work with.

Re:Chrome now uses clang for production builds on Linux by idontknow12 on Monday November 17, 2014 @01:36PM (#8619660)
Can't disagree with that. Wine vs Cedega are an example of that where the former eventually caught up and turned into something more reliable.
Re:Chrome now uses clang for production builds on Linux by fixermark on Monday November 17, 2014 @01:07PM (#8619463)
To flip the thought: If the license forbids you from building a competitive advantage, why contribute at all?

There have been issues with GCC for over a decade that go unfixed and unchanged because it doesn't make the most business sense to contribute to it. In the category of interoperation in particular, the GCC project proved to be openly hostile to the notion; they left a wide gap in the market for Clang/LLVM to fill.

Re:Chrome now uses clang for production builds on Linux by idontknow12 on Monday November 17, 2014 @01:27PM (#8619603)
The model might differ for copy left licenses, but nothing really prevents it at the end of the day. I think GCC's arcane code base made the situation worse versus business sense. Otherwise Red Hat or MariaDB would be dead.

Does it matter if my competitor can take advantage of my bug fix in a compiler? I don't think copy left licenses are a good fit for every project, but there is certain infrastructure in the world where ideally everyone can benefit.

Re:Chrome now uses clang for production builds on Linux by kllrnohj on Monday November 17, 2014 @01:08PM (#8619472)
> We have seen this type of stuff on Android with Dalvik (where Qualcomm has a special library / modified version of the VM).

Which they achieved at the cost of correctness: https://code.google.com/p/android/issues/detail?id=58726#c10

And vendors do contribute performance patches back to AOSP. ARM's Linaro group has updated & NEON-enabled some libraries, Intel contributed SSE optimizations and x86 support in general, Nvidia contributed NEON optimizations, Imgtec for MIPS support, etc...

There's a cost to maintaining a downstream fork, and a slight competitive edge tends to not actually be significant enough to justify the engineering cost.

Re:Chrome now uses clang for production builds on Linux by angersock on Monday November 17, 2014 @12:38PM (#8619293)
Yeah, and nobody was ever able to move to another web server again, and now we're stuck with Apache forever. Forever.