The time has come: Wasp 1.0 is now officially in the works! ETA: ~6 months.
Even though still young in framework-years, Wasp has been around for...
For further actions, you may consider blocking this person and/or reporting abuse
Good luck with the upcoming v1.0 release.
Also,
I wish everyone would use this definition!
I vote for "complete stack" as a new expression :D
agreed :)
Great work! 🚀
I’m really looking forward to seeing where Wasp goes with 1.0, especially the TypeScript Spec and Full Stack Modules.
Excited to follow the journey! 😸
🔥🔥🔥
Five years in beta before calling it 1.0 is the honest part — most frameworks would have shipped the label years earlier. The Spec move is what I'd actually watch: admitting the custom language was a mistake and moving to TypeScript without giving up the managed-experience vision. Do the Full Stack Modules survive that move intact, or is that where the 1.0 scope gets hardest?
The DSL-driven, convention-over-config approach is the same bet we keep making on the desktop side: in Electron projects, window definitions, IPC channels, and build configs end up duplicated across every new app, and a small manifest that declares which window talks to which channel removes a whole class of wiring bugs. Five years in beta before 1.0 is a credible signal — the hard part is not the features but keeping the abstraction stable enough that existing projects trust an upgrade. Looking forward to seeing how the managed deployment story generalizes beyond web-only targets.
Super excited for this! Just having Auth module that is easily extensible and comes as a part of a framework is already a big thing for me.
Nice stuff!
White Anglo-saxon Protestant?
🙌🙌🙌 it’s coming!!
Clean architecture is easy to maintain in a slide deck; the real test is how gracefully the system degrades under cascading production failures.
Minimizing abstraction layers and owning your critical runtime path will always outperform adding more third-party glue.
Can't wait to see it reach v 1.0!