Interview of Mark Rendle
summary
Argues that null is a billion-dollar mistake with concrete examples of crashes and null reference exceptions, contrasts fixes: TypeScript only helps at compile time while runtime is still JavaScript, C# and Java nullable-annotation compiler checks, and Rust Option type which forces handling at compile time. Presents practical patterns like empty string/array instead of null, tradeoffs between verbose safe code and developer productivity, and where a true “no value” must still be represented and checked.
AI-written summary · about
related talks
01h 13mNull & Void – Everything About Nothing in .NET
57mNullable reference types — advanced guide
52mPreventing null pointer exceptions at compile time
40mWhat's up with Rust?
35mLet’s Talk About Rust
50mConfessions of a Rusty Java developer
46mKeynote: Rust is not about memory safety
58mRust for The Curious C++ Developers