GoingNative 2012 - Day 2 - Clang
aghuttun1 HN recommenders · 2015–2022
13K views · talk · dated · Uploaded 2013-01-18
Chandler Carruth's GoingNative 2012 talk on Clang, covering how the compiler helps defend C++ code from mistakes. It makes the case for Clang's diagnostics and tooling.
Cited in discussions of why Clang exists and its case against GCC.
38:47RailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
36:45Rich Harris - Rethinking reactivity
You Gotta Love Frontend
1:12:27CppCon 2015: Andrei Alexandrescu “std::allocator...”
CppCon
51:18Lexical Scanning in Go - Rob Pike
GoogleFOSSSydney
![Video frame: William Byrd on "The Most Beautiful Program Ever Written" [PWL NYC]](https://i.ytimg.com/vi/OyfBQmvr2Hc/hq2.jpg)
1:31:06William Byrd on "The Most Beautiful Program Ever Written" [PWL NYC]
PapersWeLove
40:20"Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson
Strange Loop Conference
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
54:20Bret Victor - Inventing on Principle
Rui Oliveira
3 comments from Hacker News
Agreed, Chandler from Google makes the good case here for Clang. Chandler Carruth - Clang: Defending C++ from Murphy's Million Monkeys GoingNative 2012 - Day 2 - Clang [VIDEO]
> both clang and GCC are viable bases from which you make your internal tooling. License is not the only factor determining usability of a compiler wrt interfacing with external tools. GCC was deliberately designed to prevent such usage. See [VIDEO] at 2:22 for a direct quote from RMS on this topic.
Related, the reason why Clang was created is because GCC was specifically made to prevent it from being used with non-free software. You can find that quote around 3:17 of this talk: [VIDEO] It turned out to be easier in the long run to write a compiler from scratch, than to work with GCC.