3 ms·
React and it's model are great. React Native on the other hand is leaky, heavy and you'll spend a bunch of time fiddling with packages, upgrading them, tracking
by jamil7 7y ago
React and it's model are great. React Native on the other hand is leaky, heavy and you'll spend a bunch of time fiddling with packages, upgrading them, tracking down weird linking issues and ultimately writing some Objective-C / Java code to debug / glue / fix whatever native API you're dealing with. Thats only from my experience though. I would much rather the Compose / SwiftUI direction.
- gnusty_gnurc 7y agoThis is exactly my experience too. It’s an absolute nightmare juggling three package managers at once.
- Eric_WVGG 7y agoI had a similar experience. I was also frustrated by the Redux stack, which was odd because I quite like it on web. But in RN, I kept thinking over to how networking and data work in Cocoa Touch and Swift and wondering why we were building these byzantine solutions to problems that iOS already had built-in, elegant solutions for. Now I’m digging in to SwiftUI, which seems to take best from AppKit and React... I don’t think I’ll be doing another RN project.