Type Safety Or Security Theater: Using Servant And Yesod As Case Studies
summary
Argues that strong types can be genuine safety or just costly ritual, backing it with concrete comparisons: error handling patterns in Go, Rust ergonomics, the TSA example costing $9.8 billion and failing 80–95% of secret‑shopper tests, and library case studies Servant versus Yesod. Notes a released helper library (servant combinators / servant‑minators), shows what changed in code, and reports the tradeoffs: type safety buys different guarantees and different developer friction depending on execution.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:09Beyond marketing hype
- 3:45Cost-effective solutions
- 8:05Go vs Rust errors
- 13:26Rust thread safety
- 21:39Borrow checker tradeoffs
- 25:54Rust error idioms
- 28:01Yesod and Servant intro
- 35:11Yesod vs Servant APIs
- 44:21Type systems impact
- 47:13Senior engineer choices
- 49:03Rust vs Haskell preference
- 52:16Q&A
related talks
42mFriend or Foe? TypeScript Security Fallacies
18mScalable Bug Detection for Internally Unsafe Libraries: A Logical Approach to Type(…)
32mSafer Code with LLMs: Scala Types Silver Bullet?
59mSecure Coding Back to Basics
38mSecurity Styles
22mHigh(er) Reliability Software Patterns for Go
22mWhat Could Go Wrong? The Subtle Science Of Coding for Failure
25mSecurity First