Can someone explain this to me? Is it as bad as they suggest?

[G+_Quadflyingmedic]

Can someone explain this to me? Is it as bad as they suggest?

https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889

[G+_Jeff Brand]

For the application/use-case he cares about, it's as bad as he's benchmarked. What does bad mean? Degraded user experience in the form of poor application behavior. It's a subtle but important thing for usability.

 

Some people may turn away from Android if it continues to earn a reputation as a slow performer. As an example, the hosts of AAA have frequently complained about audio latency. I'm considering an iPod Touch as a camera simply because it's response to the shutter tap is fast compared to any Android device I've ever used.

 

Some of this can be addressed by further efforts to optimize the JS engine in Chrome, something that Google has been focused on for a long time. I don't know whether the state of the art has made it from desktop Chrome builds into the mobile version. Mobile-specific work can push this even further. The rest of it is up to the manufacturers to build/use better processors.

 

It's becoming clear that Apple really does work hard to make high quality hardware internals. Recently, Leo was talking about how Apple designs custom flash controllers for their devices to get the max performance. (I am still bitter about my Nexus 7 2012, the prime counter example in Android.)

 

Manufacturers like Samsung have been raising their game as far as external build quality. Perhaps it's time they focus "inwards", stop fighting the 4K display or ridiculous number of core spec wars, and get back to the processing and power-efficiency fundamentals.

 

It wasn't that long ago that iOS had their own severe issues with JS execution. They've made up ground, according to the author's benchmarks and it's time for the Android world to react - to the benefit of the mobile platform ecosystem as a whole.

 

HTH. :)