5 Years and $5M Later: Inventing a New Programming Language for Web Development Was a Mistake
Summary
Wasp explains why its attempt to create a universal web-development language wasn't a good fit, and why the team pivoted to a TypeScript-based approach while preserving Wasp's high-level app specification capabilities. The article highlights the challenges of language tooling, IDE support, and market adoption, and argues that a high-level spec is the core value, not the custom language. It serves as a cautionary tale for language-driven architecture in startups.