Yet another steaming pile of overengineering, great.
Multithreaded rendering on Android
21–22 of 22 posts
Re: Multithreaded rendering on Android
#22Erm, android already does multi-threaded rendering via HWUI[1] at the Canvas level. What they're talking about doing here is multi-threaded layout which isn't nearly that impressive. Heck, you can call measure()/layout() off-thread right now on views, there's just an invalidate when they get inserted into the hierarchy. Also something not mentioned is that each CPU core you spin up is eating into XX% of your battery…
Indeed, moving to multiple cores is about doing more work faster which has a direct impact on battery life. You'd have to measure whether this allows you to race-to-sleep faster or not which is a delicate balancing act. It is telling that battery life is almost never mentioned or discussed in depth anywhere. What is the battery impact of React Native? Or of this solution?
Battery life has been a major focus 2 or 3 iterations of Android ago.
Google released the tool they created in order to benchmark it (battery historian). btw, releasing the tool they created for a specific improvement is what they do each time they focus on improving one aspect of the platform, and that's an excellent practice.
Google probably cares to some extent about battery life. I doubt that the mobile team behind let's say Youtube cares, but the framework team does.
Third party devs tend to do not worry at all about battery life .. unless they use a really excessive amount of battery and are shamed for it