The founders of Wasp, a full-stack web framework for JavaScript, reflect on five years and $5M spent building a custom programming language (DSL) as the configuration layer for their framework. They explain why they originally chose to create a new language (clean syntax, runtime-agnostic vision, and personal excitement about compilers), what went wrong (developer skepticism, IDE tooling burden, positioning confusion with 'wasp-lang'), and why they're now replacing the custom DSL with a TypeScript SDK. The core insight: the value was never the language itself, but Wasp's ability to maintain a high-level understanding of the entire app at compile time. The TypeScript SDK preserves that while eliminating years of friction.

17m read timeFrom wasp.sh
Post cover image
Table of contents
TL;DR ​Why we thought creating a new language was a good idea ​Reception: You loved the idea and tolerated the language ​Goodbye Wasp language, welcome TypeScript ​DSL, thanks for all the fish - we'd never come this far without you ​Your AI agent might like Wasp, too ​We are shipping TypeScript-first Wasp soon ​
10K Impressions