How lang will wasp stay in beta?
First of all thank you for building wasp!
I have been working with it now since end of June and while it was confusing at he beginning that some things just happen automatically under the hood and can’t be changed such as Language on log in pages , I now love it and am building my startup around it.
I just am a little concerned because it’s still in beta. Do you know when it will be moving to the next stage? What are the reasons it’s still in beta? To me it seems super stable already. Never had any issues in production I didn’t cause myself.
I just am a little concerned because it’s still in beta. Do you know when it will be moving to the next stage? What are the reasons it’s still in beta? To me it seems super stable already. Never had any issues in production I didn’t cause myself.
5 Replies
Hi @fred-123. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Thank you for your kind words about Wasp and for sharing your experience! I'm glad to hear you're enjoying working with it and even building your startup around it. Let me address your questions about Wasp's beta status based on the information available in the knowledge sources.
Regarding when Wasp will move out of beta, there isn't a specific timeline mentioned in the provided sources. However, we can gather some insights:
1. Wasp is actively being developed and improved. The team is working towards reaching version 1.0, which typically signifies a stable, production-ready release. As mentioned in the Discord conversation about business model, they are "now focusing on the core product (Wasp) to reach 1.0".
2. The project is backed by Y Combinator and other investors, which allows the team to focus full-time on Wasp development. This suggests a commitment to bringing the project to maturity.
As for the reasons it's still in beta:
1. Ongoing development: The team is continuously adding new features and improvements. For example, they recently released version 0.12 with support for Node 20 and are planning to expand compatibility with other package managers beyond npm.
2. Ensuring stability and completeness: While you've found it stable in your use, the team is likely working on covering all edge cases, improving documentation, and ensuring the framework is robust enough for a wide range of use cases before declaring it out of beta.
3. Community feedback and testing: Beta status allows the team to gather more feedback from users like yourself and make necessary adjustments before a full 1.0 release.
It's worth noting that being in beta doesn't necessarily mean the product isn't production-ready. As you've experienced, Wasp is already stable enough for many production use cases. The project testing documentation mentions:
Wasp is in beta, so keep in mind there might be some kinks / bugs, and possibly some changes with testing support in the future.This suggests that while the core functionality is stable, there might still be some areas that could see changes or improvements before the full release. Given your positive experience and the active development, it seems Wasp is on a good trajectory towards a full release. If you have specific concerns about long-term stability or feature support, I'd encourage you to reach out to the Wasp team directly through their Discord channel, where they are known to be responsive and helpful. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @fred-123, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
We are working towards a 1.0 stable release during this year. We are in beta because we keep experimenting with the best API design and don't want to lock ourselves in into supporting some API we believe is wrong.
The good thing is that we don't often make breaking changes, but when we do, we offer migration paths. If you take a look at version
0.14.0 migration guide, you'll see we decided to use Prisma file directly: https://wasp.sh/docs/migration-guides/migrate-from-0-13-to-0-14
For example, in 1.0 the way you define queries and actions (operations) might change somewhat, but we will still have the concept of operations. Most of your Node.js will probably stay the same, maybe some imports / function calls would be different. This shouldn't be a surprise since Wasp is mostly glue and you write most your code in React and Node.js which mostly stays the same across different Wasp versions.
cc: @martinsos @FilipMigration from 0.13.X to 0.14.X | Wasp
This guide only covers the migration from 0.13.X to 0.14.X. If you are migrating from 0.11.X or earlier, please read the migration guide from 0.11.X to 0.12.X first.
Thanks for the thorough response. That gives me a lot of peace of mind.
You guys do amazing work!
Thank you for your feedback @fred-123 , it's super exciting to hear you find Wasp useful 🙂 As Miho mentioned, we're now working full speed towards 1.0 and will also soon share some more exciting company-related news 🙂
Btw, could you share a bit more about what you are building? Would be awesome to learn more and support you if we can!
Will send you a direct message.