this post was submitted on 22 Mar 2024
52 points (100.0% liked)
Technology
37551 readers
301 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
Delay after starting an app is essentially not a problem anymore. Most apps now come with a splash screen, so you get at least some feedback.
Lag while scrolling is still horrid. This has to do with Android apps generally being written in Java or Kotlin, which use a Stop-The-World Garbage Collector for memory management.
So, you shouldn't expect this to be fixed any time soon.
Nah, it's not GC unless lists are really poorly implemented.
Hmm, you probably mean lists shouldn't be creating new objects (/allocating new memory) while just scrolling.
Which, yeah, I remember a colleague knowledgeable about Android saying that a
RecyclerView
specifically re-uses allocated list elements.And from the little bit of Android dev I saw, it also looked like all the APIs are designed to stop you from doing(/allocating) much while the user is merely scrolling. Then, I'm not sure what's causing the lag...
Yep, that's the case. Who knows what's causing lags. It still can be a poorly implemented list, it could be OS doing something else it could be something else. It would be interesting testing same app on different devices.