r/javascript • u/Martinsos • 5d ago
Wasp web framework v1.0 is coming: the roadmap and what changes
https://wasp.sh/blog/2026/10/20/wasp-1-0-is-coming5
u/devtools-dude 5d ago
"We designed our own custom declarative language for describing a web app at a high level (the "Spec") and its own custom compiler."
Pass
17
u/Martinsos 4d ago
If you read just a few characters more, you will learn that we ditched it and are now doing it all in TypeScript!
1
u/devtools-dude 4d ago
Thanks for the update. I noticed you made a change to the copy to reflect that. I would also just make a brief note that it is now in Typescript instead.
This does make me want to investigate further and poke around a bit more; the full stack module concept sounds interesting. Although I'm not a fan of next.js, the wasp stack would be a great starting place like for people like my sibling who has no technical knowledge but wants to use AI to build something and needs a batteries-included framework to work with that can be easily deployable.
Although us technical folks understand what's required to get a prod environment up and running in most cases, people like my sibling do not and at least have some knowledge that they need some kind of platform and place to host but don't know what to do / choose.
2
u/Martinsos 3d ago
Good to know! I am highly technical yet I would also love FSMs because they allow me to bring full piece of functionatliy that somebody tested well and there is no critical wiring to be done.
p.s. you said you noticed I made a change to the copy to reflect what I said above, but I made no changes to the copy, it was like that from before.
11
u/editor_of_the_beast 5d ago
It’s so interesting what different people’s sensibilities are
I read this and I am very interested.
1
u/Biohacker_Ellie 5d ago
Agreed! The ai tech bros have drive me to look for absolutely anything other than react slop
4
u/KaiAusBerlin 5d ago
Try sveltekit 🤷
0
u/editor_of_the_beast 4d ago
Sveltekit is nothing like this. I like the ideas presented _here_ I don’t need a random unrelated framework brought up.
1
u/Snapstromegon 3d ago
Lit is IMO nearly perfect here. No transportation needed and fairly easy to replace, because it's so close to the web standards that even your HTML is really HTML and not JS in disguise (like with JSX).
6
u/Big_Muffin8280 3d ago
Fair point from the thread: AI makes the framework feel less important, but I’d argue it matters more. When you’re reviewing code you didn’t write, a framework with clear conventions and less boilerplate makes it much easier to see what the AI actually changed. Wasp’s idea of tested full-stack modules also fits this, since you reuse something that already works instead of reviewing fresh wiring every time. For me, the real test is how fast I can read and trust the generated code.
3
u/cmdr-William-Riker 4d ago
Not a bad idea, what's the advantage over using something like Nuxt or Next or SvelteKit though?
-1
u/gizamo 5d ago
It's been around for 5+ years, and v1 is still 6+ months away? That's crazy. That dude replicating Adobe products will have moved into the web world by then, and we'll have a brand new version of Magento Adobe Commerce and maybe even a version of AEM that'd doesn't completely suck.
4
u/Martinsos 4d ago
It is very different though designing something novel vs replicating an existing solution. Not to mention this is a web framework, and we can't ship slop to people that are building apps on top of it, the game is quite different. I am not saying I wouldn't love us to be faster, we are trying to understand how we can get better, but there is a lot of learning, experimenting, team-building, and innovating in those 5y. And using AI to deliver something is not as fast as one would think when you need to deeply understand what you are building.
1
u/gizamo 4d ago
I was mostly joking, but yes, that seems very slow for modern development. I'm guessing it's a very small team, which is fine. That said, you honestly lost me with:
...currently based on React + Node + Prisma...
Many of us already have our own React starter kits that we've built ourselves over the last decade+, and in the age of AI-driven development, React/Next isn't our preferred library/framework any more because it eats tokens like a rabid Tasmanian devil. A lot of the agencies we work with are also moving away from React for that reason. Please don't take that as any criticism; it's just information that might help.
2
u/Martinsos 4d ago
Sure love the info! There are different audiences for different solutions. Btw what are you using, since you mentioned it's not React? I didn't look much into it but I assumed React would be fairly token efficient due to how mainstream it is.
1
u/gizamo 4d ago
React is verbose due to explicit hooks, returns, JSX, etc. That adds up. We use Svelte for most new builds, and we moved our old Angular apps to Vue. For a few ecommerce apps, we use Marko. Interestingly, Marko is by far the most efficient with tokens (and it's not even close), but it also doesn't have massive sets of training data, which results in it making more mistakes, and then it uses more tokens to correct those mistakes. After you use it for a while and train your models, it's amazing. That said, it's also hard for devs to learn because there's not a ton of training material out there. I don't really recommend it for that reason, but it's worth mentioning because of its efficient use of tokens. Anyway, the next most efficient was Sveltekit, then Vue/Nuxt, then React/Next, and then Angular (React+Next is often even worse than Angular). But, all of those have tons of training data, so the models make way fewer mistakes. Also, because devs already know them, they're easier for devs to fix manually if/when needed. So, for those reasons, they're much better initially.
Marko has its own backend system that's impressively efficient, but for the others, we use C#, Python, PHP, and Node. Python is the most efficient, PHP and Node are less efficient but similar to each other, and C# was the least efficient. I can't say if that holds true across the board, but it's a noticable trend in our 100+ apps.
Oh, and worth mentioning for the comedy of it, WordPress is horribly inefficient for tokens. It uses 2-3X the tokens of the Laravel apps we built to replace them, which used ~2X the tokens of the Sveltekit apps that replaced them. But, Adobe Commerce was vastly, vastly worse. It was something like 5X of WordPress+Woo.
37
u/CodeAndBiscuits 5d ago
It must be so hard to launch a new framework right now when so many people are generating things with AI to a depth that they barely care about the framework they use anyway...