Why the Ultimate Web Framework Will be a Language (DSL)
summary
Argues that a web framework built as a DSL can describe the what across frontend, backend and database and then generate working code; demonstrates Wasp generating React and Node with Prisma from a single config, adding Google and GitHub auth via a one‑file spec and a generated wasp.out project that runs. Claims beta since early year, ~15,000 apps created, first Wasp-made product acquired, Y Combinator backing and nearly 4,000 stars on GitHub, pitching a full-stack DSL approach.
AI-written summary · about
chapters (9)
- 0:00Why build a new framework
- 1:50What is a DSL
- 3:57Why use DSLs
- 8:28Marrying DSLs and web dev
- 10:14DSL for authentication
- 12:48Building a full app DSL
- 16:18How Wasp works
- 19:46Moving to the 'what' world
- 20:29Introducing Wasp
related talks
45mWasmer Things: An Upside-Down Guide to WebAssembly
27mEvolution of Wasm: Past, Present, Future
49mWasmer Things: An Upside-Down Guide to WebAssembly
37mDecoding the hype behind WebAssembly: Looking under the hood
32mWebAssembly Demystified
35mWebAssembly: now web is a new compiler target architecture
17mIncrementally Extending WASI 0.2 to 0.3 and Beyond
43mLivecoding a WebAssembly interpreter