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
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