A New Kind of Abstraction
summary
Argues that abstractions are a spectrum determined by where code runs and what escapes exist, not just how high-level the API is. Gives concrete contrasts: Node vs Deno vs browser, web-first code that runs on native, and real escape hatches like Python/Lua dropping to C. Notes trade-offs: bigger final bundle, missing native APIs in webviews, and that going web→native is usually easier than native→web. Mentions Ionic, canvas examples, and practical platform testing as the proof.
AI-written summary · about
chapters (5)
related talks
36mOn the Spectrum of Abstraction
19mFinding Your Abstraction Sweet Spot
45mEscape Hatch Pitfalls
45mAbstraction Considered Harmful (and other opinions about writing maintainable code)
07mAbstractions in Angular
27m"Abstractions are Dead, Long Live Abstractions!"
25mThe Intro to Abstraction I Wish I'd Received
23mThe developer experience gap