# 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:** [9월 29, 2015, 11:25오후 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:** 249

<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: [9월 22, 2017, 9:33오전 UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/249 "2017-09-22T09:33:50Z")

</div>

Impressively, I just tested @zogstrip’s Nexus 6p on [emberperf.eviltrout.com](http://emberperf.eviltrout.com), render complex list, 2.11 and I got ~150ms. That’s quite good.

| | |
| --- | --- |
| Chrome 55 | 212 ms |
| Chrome 58 | 175 ms |
| Chrome 61 | 150ms |

That puts it in iPhone 6 territory, which is about where it should be based on the CPU, and I would rate it as solidly “good”. The Nexus 6p is not exactly a new device.. we’ll see where Snapdragon 845 takes us. Current rumors say:

> The Snapdragon 845 scores 2600+ in GeekBench 4, for single core results.

That’s about 10% faster than iPhone 6s.

---

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