A Dangerous Game: Safety in Ruby
summary
Argues that adding static types prevents common runtime failures, demonstrating an option type that eliminates nil errors and a compiled Idris example where a nonempty Vector refuses to compile, so those bugs never run. Compares Haskell/Scala style inference and Erlang’s dialyzer and mentions Michael Bernstein’s Ruby annotation tool that stops unproven code from running. Shows a tiny Ruby method with absurd test bloat (joked 244 tests) and explains where types reduce debugging time.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:17Ruby Errors
- 4:35Static Typing
- 6:27Static Typing Example
- 9:59Undefined Methods
- 12:21Testing Libraries
- 14:23Incorrect Output
- 16:12Head
related talks
37mTypes and Ruby Programming Language
31mKnow Your Types - Bringing Static Types to Dynamic Languages
30mDucks and monads: wonders of Ruby types
39mThere are no rules in Ruby
53mAn introduction to typed Ruby programming
37mChecking Your Types: An Overview of Ruby's Type System
39mSteal This Talk: The Best Features Ruby Doesn't Have (Yet)
29mRoasting the Duck - A talk about Ruby and types