4 ms·
Do you think that's appropriate for React Native? Many of the others on their list of notable projects would probably be considered "production" quality if you
by hashkb 5y ago
Do you think that's appropriate for React Native? Many of the others on their list of notable projects would probably be considered "production" quality if you asked the average dev and didn't mention the version number.
- williamdclt 5y agoI would think that's appropriate for React Native. It depends where you draw the line of "production-ready", but React Native falls short on a number of criteria (stability or bug-freeness for example). It's just a damn useful tool, despite its many shortcomings.
- jrochkind1 5y agoto me production-ready means ready to be used in production; If you and many people consider it useful enough to be used in production despite shortcomings, and are doing so, if the developers are aware of that and don't discourage it (does any react native documentaiton anywhere say not to use it in production?), and perhaps encourage it... it sounds production-ready to me.
- dcow 5y agoSo other people are the only ones who know when my project is done? And if people start using my project in production I have to immediately bump the version from 0.4 to 1? This doesn't make any sense…
- hashkb 5y agoRight, I'm with you. I think maybe the whole "we should all version the same way" thing probably isn't the right answer to "how do we know when it's safe to upgrade" question.