|
|
|
|
|
by WildUtah
4518 days ago
|
|
The jankiest thing about Android (well, aside from crappy manufacturer skins and undeletable carrier spamware) is the pauses and delays in user response. Those all come from the disastrous choice to use Java as a programming language. User facing software always feels slow when it's subject to the performance losses of automatic memory management. Java is inherently garbage collected and low power mobile devices just multiply the performance failures inherent in that design. Garbage collection is actually better for performance where instant response isn't important, such as in servers. In UI and realtime it always seems janky and slow. But even the choice of Java is related to multiple hardware vendors. There was some idea initially that Android might run on non-ARM platforms. That hasn't turned out to be an important use of Android, but it probably helped push Android to Java initially. |
|
And there is also the fact that I know it's not true because my phone (LG G2) has no problems with touch response.