News for hackers. Stuff that matters.
Re:Bringing Clang to Windows by davidgerard on Friday May 01, 2015 @06:21PM (#9474881)
I will not believe this falsifiable claim without numbers. FreeBSD has almost no users compared to Linux.
Re:Bringing Clang to Windows by feld on Friday May 01, 2015 @10:59PM (#9475693)
Define "user". You're on the internet. The bits you're downloading are probably passing through devices somewhere in the path that run FreeBSD.

~30% of North American traffic is from Netflix, whose servers are FreeBSD.

Everyone is a FreeBSD user and they don't need to know it to for it to count. Nobody actually gives a shit about numbers of users sitting on FreeBSD desktops.

Re:Bringing Clang to Windows by CurtHagenlocher on Friday May 01, 2015 @06:26PM (#9474908)
Unless you think of iOS and OS X as flavors of FreeBSD.
Re:Bringing Clang to Windows by Alphasite_ on Saturday May 02, 2015 @02:46AM (#9476144)
Isn't Darwin forked from BSD proper, instead of FreeBSD etc?
Re:Bringing Clang to Windows by davidgerard on Friday May 01, 2015 @06:28PM (#9474922)
Mac OS X is separately accountable, and that's <i>entirely</i> because Apple hates GPLv3.
Re:Bringing Clang to Windows by tzs on Friday May 01, 2015 @08:29PM (#9475356)
That's not correct. Apple needed technical things from a compiler that gcc could not feasibly do, and started moving things to LLVM before GPLv3 was released. Even if gcc had been relicensed under a permissive license such as BSD, Apple would have moved to LLVM and Clang.

A couple examples. Core Image needs an optimizing JIT compiler that can take a chain of image filters and turn it into a single efficient filter for execution on the GPU or CPU (whichever will be faster on the particular system for the particular effects). XCode needs to parse C/C++/Objective-C code in the editor and in the debugger.

What Apple needed for these things was a modular compiler system, designed to work as a compiler toolkit from which you can pick and choose the parts that you need for your particular needs. A compiler toolkit that is designed to be easy to interface with outside tools.

Gcc was explicitly designed to not be that. It was only competition from LLVM/Clang that forced some liberalization onto gcc.