A Story About Types and JavaScript
summary
Claim: adding static types cuts runtime surprises, documents intent and lets compilers catch errors early. Examples: TypeScript (a superset with its own compiler) and Flow (static checker) both land in real codebases — Slack and others migrate — and FreeCodeCamp tops GitHub with ~300,000 stars showing JavaScript scale. A runtime tool, Flow runtime, inserts assertions that throw on mismatches. Elm compiles into code with no runtime errors. Recommendation: adopt types incrementally for large projects; they work and they scale.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:44Free Code Camp
- 9:20Coffeescript
- 9:54Google Web Toolkit
- 12:12Flow
- 12:40Typescript
- 15:02Slack Switching to Typescript
- 17:21Elm
- 19:36Would You Recommend Adding Types to an Existing Code Base Which Is Rather Large
related talks
25mWhy static types in Javascript? — Preethi Kasireddy
22mType Systems Will Make You a Better JavaScript Developer
30mThe Fun of Runtime Type Systems (or "Funtime Type Systems")
01h 11mTypeScript: Static types for JavaScript
24mTypeScript: Static types for JavaScript
53m"Strict" JavaScript: Types Versus Reality
16mAll aboard the type train
28mPractical Confidence: Using Types to Help Your Computer Help You