5 ms·
> The continued React Native tax of unnecessarily difficult upgrades, My very first experience of RN was having to update an app to handle the mandatory change
by zero_shift 25d ago
> The continued React Native tax of unnecessarily difficult upgrades,
My very first experience of RN was having to update an app to handle the mandatory change to 64 bit APKs
Which required a massive update not only to several dependencies but also xcode, iOS frameworks, the weird objective C caches that get smuggled into node_modules, _as well as_ all the rigmarole or making the 64 bit APK build work
It was completely miserable
- sunaookami 24d agoIt's still like this and now they release new versions and breaking changes way faster. Not to mention they nudge you to Expo now and outsourced nearly everything to other (outdated) dependencies and companies. Stay far away from RN if you value your sanity, it lead to my burnout.
- nwienert 24d agoThis is not true, the last few releases have had almost no breaking changes. There was a really bad period during all their big refactors but they've since corrected for that. And as for outdated dependencies, breaking changes, and unfriendly companies, the reason I ever got into RN was after trying to build an iOS app using SwiftUI (and then bailing to UIKit to no avail). Talk about a borked ecosystem. The frameworks, developer tools, languages, and iteration speed of RN hands down beat any one platform, and you have one model for your data and state which is an unequivocal win. I agree it has plenty of warts, but the arc of progress is that they have been going down steadily. If you're a 3k person developer team where 200ms can cost millions a year, then by all means go purely native. Though I bet if they'd just gone to the new architecture and spent 1/5 of the cost in agents optimizing things and building a few native bridges they'd have nicer apps and be shipping faster.