3 ms·
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
by jasondclinton 7y ago
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.
- pspeter3 7y agoYeah, I wouldn't expect that either. It's the only one not using native components as far as I know.
- hanniabu 7y agoWith native toolkits being around for so long, why do they still suck to build with?
- anaisbetts 7y agoBecause they carry around 10+ versions of compatibility debt
- hanniabu 7y agoWhy can't they release breaking changes under a major release?
- novok 7y agoBecause there are many, many angry people with existing codebases that they would break, and you would get something like the python 2 to 3 saga. iOS already pushes way too many breaking changes with every major swift release. A real break would be too much. They do it incrementally via things like jetpack compose or swift UI.
- jeroenhd 7y agoFlutter tries to offload as much as possible to the GPU I think. This means the CPU load will likely be lower but GPU usage will likely be higher. Depending on the device the app is running on, this can still make the Flutter application consume more power. I'd be interested to see the performance comparison taking into account both CPU and GPU usage.
- novok 7y agoFlutter is what I call the game engine design, that happens to simulate mobile UI toolkits. It's a native c++ render and view layer, so it has the potential to be as performant as native iOS & Android code.