Michael Seibel

Wasp-lang (Beta) - Develop web apps in React & Node.js with no boilerplate

Wasp is the fastest way to develop full-stack web apps in React & Node.js. Describe high-level features (auth, CRUD, async jobs, …) via a simple config language, and write the rest of your logic in React, Node.js and Prisma.

Add a comment

Replies

Best
Ferruccio Balestreri
So much progress so far! This looks amazing 🙌 Can’t wait to build a small app with wasp 🐝
Francesco Guerrieri
So exciting to see the Beta live, packed with a ton of amazing improvements. Let's make this product of the day! :D Keep up the good work, Martin and Matija!
Martin Šošić
Super excited we got this far, I still remember when I said that if we ever get to the point where somebody makes something with Wasp, that is it, we made it - but it won't happen :D. And now we are already so far beyond that! Long road still ahead, but so far it has been amazing, and kudos to the whole team for bringing all this together and making it happen. Full speed ahead!
Igor Jerkovic
Is it safe to use in production right now? When is the 1.0 planned for?
Martin Šošić
@igor_jerkovic1 There still might be some bugs and kinks, but you can deploy it to production, with a bit of caution! If there are any issues, we are always available on Discord. 1.0 -> not set in stone yet, but we hope to have it out in the next 6 months!
Benjamin Wolba
Congrats on the launch! Proud of the entire team, you're doing an amazing job!
Matija Sosic
@benjaminwolba Thanks Benjamin, your support is appreciated! :)
Jakov Kanaet
Can I use both Google Auth and user+pass at the same time? What about stuff like magic link auth?
Martin Šošić
@jakov_ Yes, you can use both! Although, at the moment they are not synced -> so you can't have one user using both, instead it has to be two separate users, but that is something we plan to add in the future. Magic link auth would be great -> we don't have it yet, but will likely add it in the future! In the meantime you can implement it on your own if needed.
Kiril Videlov
I think the idea behind this is pretty strong. The notion of having a language that can understand the requirements of your web app and then choose a compile target sounds really exciting and could open a lot of new possibilities. How you plan to support other languages, how much work is it?
Martin Šošić
@videlov Yes that is super exciting part! It depends, if we add them for the purpose of "jobs" (check Job feature in Wasp) than that is somewhat easier, while adding them as full languages, alternatives to NodeJS currently, would require more work, and we will probably be doing that at some point after 1.0, when we will have some more resources to work on it! Most likely python and go as first options!
Toni
This is really interesting! Great job Wasp team! I've built a lot of web apps of different shapes and sizes and I can see how Wasp could be useful in providing a standardized way to do it. Boilerplate code, as much as it is future-proof, usually slows down the initial development and makes it less challenging. Wasp comes in pretty handy to make the development faster, engining, but also future-proof. As far as I can see, Wasp DSL is well organized and gives an easy and simple to extend it with custom logic which is super important. It might be especially useful for junior engineers to get started too. Starting with a single thing is way easier and faster than N things. Btw what are you using for state management, how does it work in Wasp?
Martin Šošić
@lastre We are using react-query for interaction between client and server, and that actually mostly takes care of state management. Most people are quite happy with that + React Context. But, in case when that is not enough, users can go for Redux or some other solution as an additional state management solution! If we realize a lot of people are adding something custom we might also add support for it directly, but right now this seems to be ok balance.
Toni
@martin_sosic Awesome! React Query (with React Context) is more than enough. It is great that you can go with an additional state management solution because sometimes I tend to use Recoil instead of Redux because it is more fun to work with :D
Martin Šošić
@lastre Recoil does sound fun, I remember watching video about it. I got a feeling that it is made for apps that have a lot of duplicated / connected UI that needs to be kept in sync, which can become cumbersome in Redux, but I never go the situation where I needed. But am looking forward to giving it a try at some point! In the meantime yup, RQ + Context do a really nice job! And this comes from ex Redux user.
Matija Srbić
Great stuff @martin_sosic & @matijash!! You are getting things done so fast. Really looking forward to that 🐝 1.0 soon! :D
Martin Šošić
Thanks @matija_srbic , we have great team so things are easy then! Also excited about 1.0 :)!!!
Nodar Daneliya
Woohoo, great to see Wasp reach Beta! I'm excited to learn more about how you did all this. Is there really a Haskell compiler under the hood that powers all this?
Martin Šošić
@whatever_123 Yes, core of Wasp is implemented in Haskell -> however user's don't need to know anything about it, just use it. We were choosing between TS, Rust and Haskell, but we knew Haskell the best and it is well suited for compilers -> we think it was the right choice!