No Time for Types
summary
Argues that adding types yields real, incremental gains: using @ts-check or JSDoc catches wrong argument types without rewriting code, renaming one file to .ts surfaces build errors that get fixed by declaring strings, enums and interfaces, and a large project (Dojo) rewrites to strict TypeScript for better tooling and refactorability. Shows concrete edits—default args, aliases, enum/interface definitions—and reports that the changes compile, provide IntelliSense, and make large refactors safer.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:00Nicks story
- 2:18Gmail loading indicator
- 3:50First lines of JavaScript
- 4:29Not the best language
- 4:58My first job
- 7:58JS as the web language
- 8:22Other languages
- 9:06WebAssembly
- 12:52Frameworks
- 16:27TypeScript
- 17:57TypeScript Benefits
- 21:26JavaScript and Typescript
- 23:41Subverting the Type System
- 24:37Conclusion
related talks
11mThe Joy of Typescript
39mTypeScript: Why? When? How?
25mStatic types in JavaScript: what, how and why
40mTypeScript: State of the Union
36mStarting TypeScript Leaving JavaScript as JS
27mMatthew Gerstman - TypeScript: Seeing Past the Hype
28mTypescript - a necessity front-end tool
19mYou don't know TS: often unknown parts of TypeScript