this post was submitted on 22 Mar 2024
52 points (100.0% liked)
Technology
37735 readers
54 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm pretty sure this difference isn't real. On both, the UI is supposed to be for the UI and anything that takes longer is supposed to happen on a different thread. Even Windows Phone had that. However, in practice developers don't always do it and this isn't as great as it sounds. If you're scrolling or something and scroll faster than the background threads, it will stutter. If the app has a resource leak, it will stutter. If the graphics are too complicated, it will stutter.
RAM requirements depend on what you're doing. I had a Pixel 4 and it always ran great. I had to get rid of it because it was physically falling apart and Google stopped releasing security updates for it.