GoingNative 2012 - Day 2 - Clang
aghuttun1 HN recommender · recommended in 1 month, 2015–2022
talk · intermediate · 2015–2022 on HN
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.
Up next
1 mo on HNLiam – An Innovation Story
Apple
1 HN recommend · 2016–2020
2 mo on HN2017/08/08: James Damore and his Google Memo on Diversity (complete)
Jordan B Peterson
8 HN recommender · 2017–2018
8 mo on HNStarbase Tour with Elon Musk [PART 1 // Summer 2021]
Everyday Astronaut
11 HN recommender · 2021–2024
8 mo on HNSeattle is Dying | A KOMO News Documentary
KOMO News
10 HN recommender · 2019–2024
13 mo on HNRich Harris - Rethinking reactivity
You Gotta Love Frontend
15 HN recommender · 2019–2026
12 mo on HNLexical Scanning in Go - Rob Pike
GoogleFOSSSydney
13 HN recommender · 2012–2025
12 mo on HNWilliam Byrd on "The Most Beautiful Program Ever Written" [PWL NYC]
PapersWeLove
11 HN recommender · 2017–2026
10 mo on HNCppCon 2016: Jason Turner “Rich Code for Tiny Computers: A Simple Commodore 64 Game in C++17”
CppCon
13 HN recommender · 2016–2024
8 mo on HNClasp: Common Lisp using LLVM and C++ for Molecular Metaprogramming
Google TechTalks
8 HN recommender · 2015–2024
7 mo on HNCompiling C to printable x86, to make an executable research paper
suckerpinch
8 HN recommender · 2018–2023
7 mo on HNBreak Me00 The MoVfuscator Turning mov into a soul crushing RE nightmare Christopher Domas
Adrian Crenshaw
6 HN recommender · 2017–2026
7 mo on HNA Talk Near the Future of Python (a.k.a., Dave live-codes a WebAssembly Interpreter)
David Beazley
7 HN recommender · 2019–2025
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 ▶ this video
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: ▶ this video It turned out to be easier in the long run to write a compiler from scratch, than to work with GCC.
> 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 ▶ this video at 2:22 for a direct quote from RMS on this topic.