# 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:** 223

<div class="post-metadata">

### Author: ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)
#### Post date: [February 16, 2016, 12:40pm UTC](https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889/223 "2016-02-16T12:40:37Z")

</div>

Not very relevant to Android. Always nice to hear about JavaScript getting faster though 🙂

The biggest short-term improvement to Android speeds is coming from Discourse itself, in the form of vdom:

> [@Help us test our new post rendering engine!](https://meta.discourse.org/t/help-us-test-our-new-post-rendering-engine/39221):
>
> information_source as of Tuesday Feb 23, this code is now merged into Discourse master. How was your January? I spent mine building a new branch of Discourse which replaces our post rendering with a hand-tuned virtual-dom implementation, to get around some pathological performance issues in Ember. What does that mean? Well it means that viewing a topic should be faster here on meta. note: this branch is only on meta, not master! you will not deploy it to your installs unless you go out …

This is going to be huge, and I really hope the official announcement (@eviltrout will do a proper writeup in a blog post) sparks further debate about the state of JS on Android and what’s being done to improve it on every part of the stack – Discourse, Ember, Chrome and Android.

---

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