Dr. Strangecode
summary
Argues that common Java/C++ failures — use‑after‑free, overflows, NullPointerException, ConcurrentModificationException — come from expressible-but-unsafe patterns and asks for compiler-enforced safety. Shows Shopify runs customer Ruby scripts and cites mRuby’s ~$500k bug bounty as a C/C++ consequence. Demos Rust (1.0 May 2015), its ownership and lifetimes model, borrow rules that prevent the iterator/modify and dangling pointer cases, mutex guard RAII unlocking and poisoned mutex behavior on panic, Cargo for builds, and LLVM’s removal of overflow checks in optimized builds. Mentions Pony’s reference/capability model.
AI-written summary · about
chapters (8)
- 0:00Start
- 14:35THE COMPILER!
- 16:50RUST
- 19:25OWNERSHIP
- 31:13CONCURRENCY
- 35:52PONY
- 37:22CAPABILITIES
- 39:46EXCEPTIONS
related talks
50mConfessions of a Rusty Java developer
43mRust intro for Java Developers
56mJava Sucks (So C# Didn't Have To)
47mAdvanced Type Systems. What Java Still Lacks from Rust
46mStrengthening Java Apps: Best Practices in Secure Coding for Java Developers
46mUnsafe (and Java 9/10) (RU)
50mModern Java Puzzlers
45mFifty Shades of Java