The Road to a Statically Typed Future
summary
Claims concrete wins: using Flow vs TypeScript inference reduces runtime surprises by catching type mismatches before React Native main-thread crashes, and reliable inference actually motivates experimentation. Tools and numbers: two years of Flow in production, BuckleScript/Reason compiles to JS and to native, and a real project called Lagoon Docker deployments runs in production. Demos: a typed tic‑tac‑toe and server interop show Reason + BuckleScript works, plus React Native crash prevention is the central, practical goal.
AI-written summary · about
chapters (18)
- 0:00Start
- 7:30THE ROAD TO A STATICALLY TYPED FUTURE TYPE SYSTEM ?
- 12:12FUNCTIONAL PATTERNS
- 15:20TRUST KILLERS
- 17:42APPLICATION
- 19:41PARTLY TYPED ARCHITECTURE
- 20:22SERVER COMMUNICATION
- 22:213RD PARTY LIBRARIES
- 24:06create
- 25:57HOW TO IMPROVE ?
- 28:25REASONML
- 31:05BUCKLESCRIPT
- 31:42TOOLING
- 36:38'Pattern Matching' in Flow
- 38:30Let's design the model in Reason!
- 40:39Model Types in Action (Reason)
- 51:40RECAP
- 52:53React Alicante 2017
related talks
01h 02mThe Road to a Statically Typed Future
42mStatic Type Checking with FlowType
32mStatic typing with Flow and TypeScript
30mFlow Typing a React Codebase
23mFlow or how I learned to stop worrying and typecheck my React code
16mAll aboard the type train
06mEmpowering your React application with types using flow
28mPractical Confidence: Using Types to Help Your Computer Help You