When referring to Wasp as "Laravel for JS", it was more in the sense of providing an integrated, opinionated DX rather than being a carbon copy of how exactly Laravel works, which Adonis is definitely closer to, being a backend-first framework, while is covering the full-stack of your app.
But I understand the confusion - developers today use the term "Laravel/Rails for JS" in both ways, so it's not always clear what they want to say by it.
Maybe you should have explained yourself better. It's not about having an opinionated DX. It's about being pleasant to use and having a really GOOD DX
I would never want to use something like this over Laravel, it's not good enough.
apptodoApp{title:"ToDo App",// visible in the browser tabauth:{// full-stack auth out-of-the-boxuserEntity:User,methods:{google:{},gitHub:{},email:{...}}}}routeRootRoute{path:"/",to:MainPage}pageMainPage{authRequired:true,// Limit access to logged in users.component:importMainfrom"@client/Main.tsx"// Your React code.}querygetTasks{fn:import{getTasks}from"@server/tasks.js",// Your Node.js code.entities:[Task]// Automatic cache invalidation.}
1) AdonisJS is a better Laravel-for-JS
2) Vibe coding is not a good thing
When referring to Wasp as "Laravel for JS", it was more in the sense of providing an integrated, opinionated DX rather than being a carbon copy of how exactly Laravel works, which Adonis is definitely closer to, being a backend-first framework, while is covering the full-stack of your app.
But I understand the confusion - developers today use the term "Laravel/Rails for JS" in both ways, so it's not always clear what they want to say by it.
Maybe you should have explained yourself better. It's not about having an opinionated DX. It's about being pleasant to use and having a really GOOD DX
I would never want to use something like this over Laravel, it's not good enough.
Thanks for checking it out! Yes, Wasp is currently in Beta. We'll soon announce a full roadmap for reaching 1.0.
Vibe coding is great, if you do it responsibly :)