# The State of JavaScript on Android in 2015 is... poor

**URL:** https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889
**Category:** General
**Created:** [September 29, 2015, 11:25pm UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889 "2015-09-29T23:25:14Z")
**Posts on this page:** 1
**Showing post:** 246

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [June 29, 2017, 9:58pm UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/246 "2017-06-29T21:58:51Z")

</div>

In mid-2017, Chrome has [finally gotten their act together](http://benediktmeurer.de/2016/12/16/the-truth-about-traditional-javascript-benchmarks) on Javascript – benchmarks shown below are on a Nexus 6p:

 ![](https://global.discourse-cdn.com/meta/original/3X/3/1/31232ab5c6c845e3714964cb9c682c52028f1096.png)

Read [the official Google followup](http://benediktmeurer.de/2016/12/19/following-up-on-javascript-benchmarks) as well … all of this went into [the Turbofan and Ignition release in Chrome 59](https://v8project.blogspot.com/2017/05/launching-ignition-and-turbofan.html).

Combined with the snapdragon 835 we’re _finally_ entering `obama-not-bad.gif` territory, where a recent Android device (90ms) is at least in the ballpark of an iPhone 6s (60-70ms) when on Chrome latest, currently 59:

 ![](https://global.discourse-cdn.com/meta/original/3X/c/6/c6b8804e4f115fdcfa50dc4715bad178c44d4636.jpg)

---

_[View the full topic](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889)._