this post was submitted on 24 Oct 2024
253 points (82.9% liked)
memes
10093 readers
4212 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Funny, though they have actually been working hard on optimization too. For a great example, see changes like userfaultfd garbage collection in 13.
I feel like the whole JVM stack is just kind of a lost cause. We've been throwing bigger hardware at it and optimizing it for decades, but the crappy iPhone my workplace gave me, still feels smoother in every way...
I believe back in Android N there was a move to compile all apps to native before running. Currently, Android relies on Android RunTime (ART) and it tries to keep everything performance critical in compiled code, but it's not perfect. You do still have a JVM and there's still garbage collection.
I don't know what are they optimizing it for, when I click on something, it still takes a year to load, the only difference I feel between my current phone and my first android is that this one has a much larger screen, and this one costs 10 times more. In my opinion, android has been going backwards since around 8.0