@eviltrout I saw this post We finally did something about Android Performance | Evil Trout Inc.
After years of waiting for a breakthrough in Android or Ember performance, we decided it was time to to take the nuclear option: we replaced the Ember rendering engine for our most common view with a custom virtual DOM based renderer.
So it seems like the vdom/widget system in discourse was built as a response to the android performance issues.
This commit that introduces cloaking seems to happen after the vdom/widget system:
https://github.com/discourse/discourse/commit/cc5ca90ac6234483bf3ebf0522df4455cdb044fe
Is cloaking and the vdom/widget system in some way related? It seems like they both address performance. Recycling components would reduce the amount of dom elements significantly, so something like the vdom/widget system wouldn’t be necessary, right?