Dconf 2014 Day 2 Keynote: The Last Thing D Needs -- Scott Meyers on HackerTube: recommended by 4 Hacker News commenters across 5 separate months, 2018–2025.
talk · intermediate · evergreen
Scott Meyers' keynote at DConf 2014, drawing on 25 years of C++ experience to offer the D language community a plea about what it should avoid. It centers on the accumulated complexity and pitfalls of C++ as a cautionary tale.
HN commenters bring it up whenever C++ complexity or the pitfalls of language design come up, as a witty and authoritative warning.
“everyone should watch Scott Meyers's awesome presentation at a D conference”
11 Hacker News comments link this video. Each one links back to its thread.
Yes, and everyone should watch Scott Meyers's awesome presentation at a D conference with the title "The Last Thing D Needs". (tl,dr version: The last thing D needs is someone like him, really to be so insanely convoluted, as C++ is, as to need someone like him.) Link to the video: ▶ this video
in “Modern C++ for C Programmers (2018)” · View on HN
I'll just leave this fantastic talk here: The Last Thing D Needs - Scott Meyers (2014) ▶ this video The C++ type system really is quite... complicated.
in “Never trust a programmer who says they know C++” · View on HN
> You cannot say the same thing about Rust. At least not yet. My fear is it's _very_ easy to fall in to the same trap as C++ has, and become a big mess. Scott Meyers have a very nice talk here: ▶ this video about all these traps and pifalls that we have to deal with in C++. That said, I'm starting a bit with rust and enjoy it so a lot, especially the tooling alone is worth it - and if I never have to write another line of C++, I would be very happy (ofc the real world argues I have a lot of C++ code that will need maintenance).
in “Rust in the 6.2 kernel” · View on HN
> C++ developers .. don't seem to be interested in actually improving the language In his talks at the 2014 and 2017 conferences for the D programming langue, Scott Meyers noted the difference between what individual C++ committee members say they value, and what the process actually produces. Will a new standard every three years make this better or worse? They do seem open to deprecating things that don't work. You might enjoy the 2014 talk, called "The Last Thing D Needs." I don't want to spoil the punchline, which actually struck me as kind of bittersweet, but Scott talked about the distinction that Fred Brooks made in "No Silver Bullet" between essential and accidental complexity. C++ does have a lot of the latter. Edit: link for the 2014 talk: ▶ this video and for the 2017 talk: [link]
in “Meta Crush Saga: a C++17 compile-time game” · View on HN
We Really Don't Know How to Compute: Gerry Sussman - [link] Zebras All the Way Down: Bryan Cantrill - [link] Jonathan Blow on Deep Work: Jonathan Blow - [link] Simple Made Easy: Rich Hickey - [link] Effective Programs - 10 Years of Clojure: Rich Hickey - [link] The Last Thing D Needs: Scott Meyers - ▶ this video
in “Ask HN: What is your favourite tech talk?” · View on HN
Your point on coherence is similar to the perspective of an ex-C++ maintainer. This video came out a decade ago ▶ this video and I feel his lesson went unheeded. It's relevant to the bigger and more dangerous concept of Conceptual Integrity by Fred Brooks.
in “The Core of Rust” · View on HN
Scott Myers, author of the extremely popular Effective C++ explainers, gave up on the language because of its churn. ▶ this video
in “Writing an LLM from scratch, part 13 – attention heads are dumb” · View on HN
>I'd kill for an "Effective D" book [link] The Last Thing D Needs - Scott Meyers - DConf 2014 ▶ this video
in “Ask HN: What less-popular systems programming language are you using?” · View on HN
Instead of defensiveness, why not talk about the ways in which the C++ committee is changing how they're operating (or even leaving ISO) and changing their culture to shore up these things. Look at past Scott Meyers talks (e.g. [1]). He highlights how the committee has arbitrary set of principles that can be applied to justify or reject any proposal and the inconsistencies in the language are a reflection of this. This isn't a problem of the language itself but rather that it's design by committee with 4 major front-end implementations (Intel, MSVC, Clang, GCC although I believe Intel is standardizing on the Clang front-end at least). Organizational issues like that are tough to spot but it's become clear now for several years that Rust is going to beat C++ silly if the C++ committee doesn't clean up their act and steer the C++ community a bit better (e.g. still no ABI specification, no improvements on macros, no standardized build system, modules are a joke, no standardized package system, etc etc). They're not effective stewards not least of which because they can't even take good impactful ideas from Rust and copy them. [1] ▶ this video
in “C++ Safety, in Context” · View on HN
I'd say a lot of this is a form of survivorship bias. I've programmed in C++ since the mid 90s so I am used to a lot of C++'s issues, but I also run a company and have to train new engineers and I see first hand the absolute nightmare that a lot of people encounter learning this language and it's demoralizing. While to me a lot of this is stuff I managed to figure out, I also understand that for many new developers this is just crap that no one should have to deal with in 2023. Lack of a good way to build third party libraries, build times that are astronomical and a true productivity killer, error messages that are entirely unhelpful and can produce giant walls of text for the most trivial of reasons, rampant undefined behavior that is incredibly hard to identify. Several things changed my view on C++ and now I see it mostly as a sort of zombie language. 1. As I mentioned once I started my own business and needed to train new engineers on how to use C++, I started to look at the language from a fresh point of view and realized it really is a complex mess just to get basic things working. 2. Scott Meyers "retiring" from C++, and in particular this video: ▶ this video 3. I attended an ISO C++ meeting in Toronto and while I absolutely found that the people were very intelligent and knowledgeable, as well as well intentioned, I realized just how political C++ is and that much of its development and complexity is not due to technical constraints or driven based on what is in the best
in “Talking with the Inventor of C++” · View on HN
It is definitely related to C++ (both in ideology and in participants) and AFAIU even more features, but, for example, Scott Meyers views it[1] as having less random stupid inconsistencies than C++. [1] ▶ this video
in “Why I use the D programming language for scripting (2021)” · View on HN