blitz
blitz copied to clipboard
blitz-js
2.0 stable launch
- Product hunt
- hacker news
- office hours/livestream/q&a with special guests?
- inspiration from Redwood's 1.0 launch?
- email newsletter
Don't know if this is the place but here are my two cents:
As a dev, I would like some @alpha (pre-launch release, functional code) to test prior to a launch. Getting people to test the proposal, find some bugs, report, make noise and posts all over the internet, and even generate some "early tutorials" using the alpha release.
Everyone would know is prone to change, API can vary from the final product, but test the waters. One example that comes to my mind is React 18 and NextJS adding a Server-Side Component code in alpha.
So the "real" launch is tested, verified, and approved by several people already using the alpha, a lot of repos using it in toy projects, and a lot of social validation.
I would dare to say the @alpha approach would increase adoption even more than a flashy release announcement as it can build momentum over the product.
Hey @Israel-Laguan. We do have an alpha version currently and people are testing it and upgrading from the legacy framework to the toolkit. We first released alpha at the end of April and recently made more public announcements. Before stable, we will also have a beta release. Is that what you meant or am I missing something?
Can you kindly point me to the documentation about how to use the alpha in a new project? Sorry if I miss it. I would like to test it in a toy project I am about to start.
I came to the repo to find a way to use graphql request from a separate mobile app using the new approach, but was hard for me to find docs about it, so I would really love to test it.
I'm so excited for this, are there any updates on this? I can barely wait ahahahah
