4 ms·
This is a very interesting perspective on LLVM. I don't believe Apple has the most contributors (IE compared to the community as a whole), and i don't think the
by DannyBee 13y ago
This is a very interesting perspective on LLVM. I don't believe Apple has the most contributors (IE compared to the community as a whole), and i don't think they ever did.
They also haven't pushed it as much as you'd think.
For example, Apple had precisely nothing to do with Linux or FreeBSD support for LLVM.
Now, you could definitely make your statement about clang, but not LLVM itself. Apple deserves a lot of credit for pushing clang forward.
On the LLVM side, however, since about 2 years ago, Google has probably has as much impact on LLVM as Apple, and you hear nothing about this, because they don't hold external developer conferences talking about it.
(You can count the number of Google presos at recent developer meetings if you want a good indication of how involved they are).
Now, of course, in reality, the credit should go to the people doing the work, regardless of where they work, but HN and other places always like to set up these things up as if they are really corporate projects.
- jyap 13y agoUh, quite false in your statements and assumptions. Do you know that Chris Lattner has worked for Apple since 2005? Chris Lattner being the "primary author of the LLVM project".
- DannyBee 13y agoYou are going to have to do better than that. I've known Chris Lattner a very very long time (since before he worked at Apple), and have counseled the LLVM project on various issues since then. I was also involved in mediating the proposals to merge LLVM and GCC that came up, and I watched Chris sell Apple folks on LLVM and get hired. Chris is not a primary author any more, he is a director at Apple. Most of LLVM was not written at Apple, it was written at UIUC (LLVM was started in 2000). While large parts have been rewritten since then, it would be absolutely positively incorrect to say it was Apple's project. I don't even think Apple was the first company to hire people to work on it! Note that Chris doesn't really code much anymore (and hasn't for at least 2 years), given that he has too many people to manage. So, now, if you'd like to point out what statements you think i made are incorrect and your supporting data, i'd love to hear it.
- tedunangst 13y agoNot commenting directly on Apple/LLVM, but sometimes all it takes to make a project succeed is a big name to step in and say they support it. Even if Apple doesn't contribute a line of code, "Apple thinks LLVM is the future" brings new people into the project. (I also think people use LLVM and clang interchangeably, regardless of technical accuracy. Clearly, the evolution of clang played a big part in FreeBSD switching.)
- DannyBee 13y ago"Even if Apple doesn't contribute a line of code, "Apple thinks LLVM is the future" brings new people into the project" This is a fair point. However, I actually think GCC's negativity and steadfast refusal to adapt and evolve contributed more to its rise than anything else. Apple may have brought users. But the contributors are mostly ex-gcc folks, or folks from research communities/other compiler people. They are the people that were/would be working on GCC if LLVM didn't exist. The reason LLVM got the majority of these contributors is not because Apple made it the default compiler, or even because Apple supported it. It's because GCC was unwilling to change and adapt in the ways that its contributors (current and future) wanted. For example, becoming a modular, pluggable compiler. RMS resisted plugins for many many years. He resisted writing out the IR. He resisted requiring newer versions of C, or C++, or ... (While GCC is led by a steering committee, RMS can override them, and the recourse is to go to the FSF board or something. I can't remember all the details of the EGCS reunification agreement). The steering committee of GCC, while all wonderful people, over time became less of GCC contributors, but refused to turn over their steering committee roles to any younger and newer contributors. This left GCC with a steering committee that, while well intentioned, and again good people, was not in any way related to the current major contributors. Part of this was just politics. GCC simply had a lot of politics (because of the FSF, because of EGCS, etc) that LLVM did not. In any case, contributors and researchers left GCC because of this unwillingness to change. This is what caused a community to coalesce around LLVM, not Apple. People in this community advocated to their companies to adopt LLVM, and some were successful. This is why Apple uses it. This is why ARM uses it. It is because the community and it's members were successful in convincing them to do so (certainly, there is more, in that the companies saw long term strategic benefit, etc)