I saw that Wasp is working toward version 1.0. What changes are planned, and how are people feeling about the direction?
What's changing in Wasp on the way to 1.0?
Answers
The main change mentioned in the discussion is a move away from Wasp's custom declarative language for describing an app, toward TypeScript. The custom language and compiler were enough to put some people off, while others found that design interesting.
The discussion doesn't give much detail about the rest of the roadmap, so I wouldn't treat this as a complete list of 1.0 changes.
Reply to this answer
I can see why a custom language would be a sticking point. It's another thing to learn and a layer to understand when something goes wrong. TypeScript sounds more approachable if that's already part of your stack, though the details of how Wasp uses it still matter.
Reply to this answer
The timing got some pushback too. Wasp has been around for more than five years, and 1.0 was described as still being over six months away. That's a long wait if you're looking for a finished release.
On the other hand, designing a framework that other applications depend on is different from reproducing an existing product. A slow path to 1.0 isn't necessarily a sign that nothing useful has happened, but it's fair to ask what remains before release.
Reply to this answer
There's also the question of how a framework gets attention when so much development discussion is focused on AI. But even if an AI tool writes the code, it still has to use some underlying technology. Knowing that stack can make it easier to review and maintain what gets generated.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6k+bytewrench_742:
For some people the custom language was the interesting bit, though. A high-level way to describe an app could be appealing even with the learning cost.