GoingNative 2012 - Day 2 - Clang
Channel:aghuttun · Length:1:00:53 · Published:2013-01-18 · Views:13450
Summary
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.
Why HN recommends it
Cited in discussions of why Clang exists and its case against GCC.
Chandler from Google makes the good case here for Clang. — HN, 2015
C, C++, Rust, Go & systems languages · Compilers, interpreters & program analysis · Testing, debugging & developer tools
Subtitles (excerpt)
And one of the things I think is really cool about this is uh Chandler sort of he embodies the young the next the new generation. So um he owns Clang at Google and he's going to come out here and teach us about Clang. I don't know most of you have probably used it maybe not but come on out here Chandler. All right so I'm here today to talk to you a little bit about Clang. I want to thank uh Herb and Charles for actually inviting me to come talk to you about Clang. It's it's a really great opportunity. It's a great opportunity to get to talk to a lot of people who who may not be exposed to Clang and in kind of their day-to-day interactions with C++. Um just as kind of just just to get a feel for things. How many folks here have ever used Clang like even once? All right. How many folks here have used Clang in the last month? How many folks here used Clang because of this talk? All right, some of you aren't being honest. Okay, that's okay. So, CL C clang is really interesting and and because it's it's very new and because it doesn't support as many platforms, it's still gaining a lot of traction. I want to try and give you guys some background on on what Clang is, where it's come from. So, let's let's talk a little bit just very generally about
On 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] — jxramos, 2015-07
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. — omoikane, 2022-04
> 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. — wolfpld, 2017-08
Related videos
- Liam – An Innovation Story · Apple · 1:04
- 2017/08/08: James Damore and his Google Memo on Diversity (complete) · Jordan B Peterson · 51:10
- Starbase Tour with Elon Musk [PART 1 // Summer 2021] · Everyday Astronaut · 53:17
- Seattle is Dying | A KOMO News Documentary · KOMO News · 1:00:36
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- Rich Harris - Rethinking reactivity · You Gotta Love Frontend · 36:45
- CppCon 2015: Andrei Alexandrescu “std::allocator...” · CppCon · 1:12:27
- Lexical Scanning in Go - Rob Pike · GoogleFOSSSydney · 51:17
- William Byrd on "The Most Beautiful Program Ever Written" [PWL NYC] · PapersWeLove · 1:31:05
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Solving Problems the Clojure Way - Rafal Dittwald · Clojure/north · 1:02:26
- Debugging Under Fire: Keep your Head when Systems have Lost their Mind • Bryan Cantrill • GOTO 2017 · GOTO Conferences · 52:34
- "Performance Matters" by Emery Berger · Strange Loop Conference · 42:15
- CppCon 2017: Matt Kulukundis “Designing a Fast, Efficient, Cache-friendly Hash Table, Step by Step” · CppCon · 59:33