CppCon 2017: Titus Winters “C++ as a "Live at Head" Language”

Channel:CppCon · Length:1:31:13 · Published:2017-09-28 · Views:53107

Watch on YouTube

Summary

Titus Winters' CppCon 2017 talk argues for C++ and Google's Abseil to be maintained as a live at head language, relying on testing and automated tooling rather than never changing or promising no compatibility. It covers Hyrum's law and the limits of semantic versioning.

Why HN recommends it

Recommended whenever versioning, semver, monorepos and backward compatibility are debated, for its nuanced treatment of dependencies.

a much more nuanced look at dependencies & versioning — HN, 2020

C, C++, Rust, Go & systems languages · Software architecture & design · Testing, debugging & developer tools

Subtitles (excerpt)

- [Chandler] Good morning, everyone. - [Man] Good morning. - [Chandler] Really, oh, come on, you have to do a little better. Good morning, everyone. - [Everyone] Good morning! - Okay. So, I am super excited to be up here. Number one reason why I'm super excited to be up here, I do not have to present up here. Actually, the real reason I'm super excited to be up here is because I'm really excited to introduce your next speaker, Titus Winters. And I have a small story to tell to give you an idea of how I got to know Titus professionally. You see, my team and I, we built a bunch of C++ tools, amazing C++ tools, miraculous. We were sure they were gonna change the landscape of C++. They couldn't be beat, it was wonderful. But we made this critical mistake. We forgot something. Tools do not have impact. I know, everyone's like, wait, what? Tools don't have impact, they don't, they really don't. Tools can't change the world. People use tools to have impact and to change the world. And Titus and his team used our tools to change the world of C++ at Google. And he turned our C++ codebase from something that was falling down around us, and that we didn't know what to do with into something sustainable and maintainable

On Hacker News

Usually that problem is dealt with combination of: * Automation. * Ability to change other people's code safely, possibly gated by code review approval. Cultural and technical (e.g. unit tests must exist and be maintained) barriers may apply. * Making incremental changes that are backward compatible (at least until you migrated all clients so you can cleanup later) I recommend this talk [VIDEO] (… — ithkuil, 2020-11
> If you go listen to Google people talk about dependency/version management. It's like they think it's global lock vs inconsistency. Monorepo or chaos. This false choice irks me. I watched this talk: [VIDEO] I’d say this is a much more nuanced look at dependencies & versioning. We all know these days that something like semantic versioning is not enough, because it is too easy to depend on behav… — klodolph, 2020-10
For another perspective on “semver is a lie,” see the “Live at Head” talk from Titus Winters of the Google core C++ team. [VIDEO] TL;DW: By Hyrum’s law, at sufficient scale, there’s no such thing as a non-breaking change (including changing comments). Embrace that, and test sufficiently that you can always take the latest dependency but detect when it breaks. — s3cur3, 2020-07
Semantic versioning isn't a silver bullet, unfortunately, due to the 'Diamond Dependency Problem'. That is, A depends on B and C, but B and C depend on different versions of D. Easy to fix, until you scale that up to thousands of nodes in a dependency graph. This talk is one of the better ones about this: [VIDEO] — kinjba11, 2019-10
> You are totally correct that to achieve the same performance, correctness, and overall master level "green"ness in a multirepo system you would have to either define or detect dependencies and dependent repos, build the entire affected chain, and test the result. That part is much easier in monorepo. You also would need to do that as an atomic operation (in the mono-repo + especially with a com… — jacobparker, 2019-04

Related videos