If you’re interested in all the big refactoring projects happening in React Native right now, there are summaries here:<p>Fabric: <a href="https://github.com/react-native-community/discussions-and-proposals/issues/4" rel="nofollow">https://github.com/react-native-community/discussions-and-pr...</a><p>TurboModules: <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40" rel="nofollow">https://github.com/react-native-community/discussions-and-pr...</a><p>Codegen: <a href="https://github.com/react-native-community/discussions-and-proposals/issues/92" rel="nofollow">https://github.com/react-native-community/discussions-and-pr...</a><p>JSI: <a href="https://github.com/react-native-community/discussions-and-proposals/issues/91" rel="nofollow">https://github.com/react-native-community/discussions-and-pr...</a>
RN has been such a big boost of productivity for us, it changed everything. We were able to onboard junior developers that are excited to work with it as well as keeping our at the time existing native developers enthusiast about it (they embraced it since), and the time to market for us have dramatically improved for new features on both iOS and Android.<p>Of course some stuff sometimes doesn't work well, react-native link versus Pods, native modules or various SDK integration, navigation is sometimes tedious to work with but it is worth it really.<p>I don't regret at all the choice of migrating our app to RN one year and a half ago.
Appreciate all the work FB is doing here, but RN is fundamentally never going to be a solution for most teams. The compounding problems (JS/swift/obj-c/java) and their dependencies in the build process demand that you hire native developers. That eliminates the #1 reason to use it.<p>After 3 times using RN and having to go back to native... never again. When even simple things like navigation or animations take hours of research to get right.
I'll just plug my repo here that helps with upgrading existing RN projects to new versions.<p><a href="https://github.com/pvinis/rn-diff-purge" rel="nofollow">https://github.com/pvinis/rn-diff-purge</a>
Interesting, I thought I had seen it mentioned somewhere (Twitter, I believe?) that hooks would only be available on v0.60. Excited to see them integrated so fast!
I feel like the React Native fad has come and gone. Even FB is using their own server-driven UI solution nowadays, which allows clients to be dumber while still rendering native components.
I apologize for not really commenting on the content of the release, but I am shocked that it is on version 0.59.<p>I wonder why they even bother with supposedly following semver at this point. 0.59? This seems to mean they can break anything at any point and it's technically still "following semver". I guess I just don't understand it. This library is used by thousands and consumed by millions (billions?). Why not just use dates as versions?