"Strict" JavaScript: Types Versus Reality
summary
A small company spent a year building a “typed JavaScript”; the talk recounts practical problems and benefits encountered during that transition, and when strict typing is worth pursuing for engineering and business. It discusses type systems with a focus on FlowType and its ecosystem (and briefly explains why TypeScript was not chosen) to show what flow-based typing offers and where the typing community is heading.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:17Need for strict typing
- 2:19Types in outsourcing
- 5:31TypeScript unsuitable
- 8:50TypeScript with VS Code
- 10:21Flow better than TypeScript
- 13:10TypeScript vs Flow
- 22:46Flow’s S type trust
- 26:19Liskov in TypeScript
- 32:03Functional programming with Flow
- 37:08Flow error example
- 41:06Flow and ReasonML types
- 46:27Q&A
related talks
01h 11mStrict Types in JavaScript
27mA Story About Types and JavaScript
25mWhy static types in Javascript? — Preethi Kasireddy
24mTypeScript for JavaScripties
27mMatthew Gerstman - TypeScript: Seeing Past the Hype
01h 11mTypeScript: Static types for JavaScript
30mTypeScript: Seeing Past the Hype
28mPractical Confidence: Using Types to Help Your Computer Help You