21–30 of 186 posts
Don't miss the link at the bottom of the article to CPU utilization numbers. tl;dr: Flutter and React Native are dramatically easier to develop for than native toolkits and Flutter CPU utilization is better than native toolkits. That... is not what I was expecting.
With native toolkits being around for so long, why do they still suck to build with?
Props to the author.
This is because, based on what the author mentioned about cell reuse, they barely have any expertise in iOS. It would be hard to trust the code. Perhaps the author has provided access to the code?
I'm seriously considering rebuilding a prototype we have at work in Flutter in my spare time but I'd hate for it to be a similar situation to React Native where it appears to save me time at first and then fucks me over and only makes everything take more effort to get right.
ouch The Android code indeed looks like a copy paste of bad stack overflow answers. I can't really hold it against the author .. learning several platforms at the same time is a bit much.
Looking at Flutter vs React Native, the only comparison of interest for, perhaps most of us, Flutter for the win! Lower dev resources and way lower cpu usage. Dart is lovely, the docs are great, wide array of great UI widgets, and easy animation. As for hot reloading, well, you just have to experience the difference.
Learning a completely new language in Dart to even get started with Flutter doesn't seem like low dev resources.
With React Native you are using:
- Javascript which most devs have a grasp on in 2020
- JSX which really isn't much different to HTML
- Styling is practically just CSS with slightly different property formatting and naming
If you've decided to go down the RN then theres a decent chance that your devs have used React before and there really isn't much between React and RN.