# 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:** [29. September 2015 um 23: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:** 8

<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:** [29. September 2015 um 23:48 UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/8 "2015-09-29T23:48:04Z")

</div>

Reminder, **Angular also has this same performance problem on Android**. It’s not specific to Ember. _Any_ complex JavaScript app will exhibit the same problems.

So it’s really about throwing away the JavaScript part of the app, which is challenging since Discourse _is_ a JavaScript app. How do you throw away what you are? You can’t rip out your own skeleton.

Anyway, I agree, the 2013 me said “surely the state of JavaScript performance will improve on Android by 2016”. Sorry 2013 me, things didn’t turn out that way 😢

---

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