5 ms·
So they're going the Google Chrome route, already at v14. Doesn't really matter of course, but it's off-putting. I would have preferred them to use 1.0, clearly
by sergiotapia 11y ago
So they're going the Google Chrome route, already at v14. Doesn't really matter of course, but it's off-putting. I would have preferred them to use 1.0, clearly indicating it's production ready.
- Cshelton 11y agoRight, but they should not be indicating it's ready for production right now...simply because it's been production ready for ~2 years, stable for longer really. We have had React in production for almost 2 years...it has been extremely stable. It should be clear that React is very mature, I think 15.0.0 fits.
- lbenes 11y agoNo, this has nothing to do with Google's rapid release cycle or versioning scheme. As stated in the article, the API is stable so, it makes sense to switch to a semver scheme.[1] From an engineering perspective, this is a system that makes perfect sense for all libraries to adopt. They choice 15 as the starting MAJOR version because people already referred to 0.14.x as "React 14", avoiding any possible naming confusion. They will remain at 15 as long as there are no major features or API breaking changes introduced. [1] http://semver.org/ http://semver.org/
- sergiotapia 11y agoThank you[1] [1] Thank you
- bsimpson 11y ago> Our business as well as many of yours all depend heavily on the use of React as a core piece of our infrastructure. We're committed to the stability as well as the progress of React going forward. Yeah, it doesn't sound too stable to me either. </sarcasm>