All aboard the type train
summary
Compares actual tradeoffs: Flow is a static type checker that you opt into with // @flow and whose server sometimes spawns heavy processes, while TypeScript is a superset language where renaming .js to .ts usually boots it up and the compiler prevents shipping type errors. Shows real numbers (≈20k vs ≈47k GitHub stars, 3k flow-typed vs 22k DefinitelyTyped), notes community and tooling (prefer VS Code, migrate linters), and recommends TypeScript for new projects while acknowledging alternatives like Reason or Elm.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:27Static vs Dynamic
- 4:15Dynamic typing Cons
- 6:12Flow - static type checker
- 9:15Configuration
- 9:45Performance
related talks
58mFlow - Am I Your Type?
43mFlow - Am I Your Type?
30mFlow typing: your path from experiments to final implementation in an enterprise project
28mPractical Confidence: Using Types to Help Your Computer Help You
42mStatic Type Checking with FlowType
23mFlow or how I learned to stop worrying and typecheck my React code
22mMigrating 600k+ Lines of Code from Flow to TypeScript
27mA Story About Types and JavaScript
