Why the ultimate web framework will be a language (DSL)
summary
Argues that a domain-specific language pays off by describing what an app should do and generating the implementation: a Wasp DSL compiles to React + Node + Prisma code, handling routing, models and auth. Demonstrates adding Google and GitHub auth with a single line, and shows a visual planner. Claims success: 15,000 generated apps in one month, single-file DSL → React + Node + Prisma output, ~20,000 total apps and ~6,000 GitHub stars, YC-backed and used as a GPT-powered starter.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 2:01Why build another web framework
- 4:29What is a DSL
- 6:39When to create a DSL
- 9:53Benefits of DSLs
- 11:38DSLs for web frameworks
- 13:05Implementing auth as a DSL
- 15:57Demo of auth DSL
- 16:18Designing more DSL features
- 18:44LLMs and DSLs
- 20:10Experiment with GPT and DSL
- 21:33How Wasp works
- 23:20Visualizing DSL output
- 24:23Future of DSLs in web dev
- 25:06About Wasp and closing
related talks
06mLightning talk from John Leidegren
16mArchitecting A Component Compiler
38mWeb Applications of the Future With TypeScript and GraphQL
27mWhere is the JavaScript world going?
35mRethinking Enterprise Architectures with Node.js
46mFuture-proof your Web Apps with Web Components and LitElement
25mWeb applications of the future with TypeScript and GraphQL
36mBeyond JavaScript: The Hidden Benefit of React Native