@onemandesignarm @codinghorror V8 (chrome/android) is gambling pretty hard, whereas JSC (safari/iOS) has been more conservative...
-
-
Replying to @stefanpenner
@onemandesignarm
@codinghorror ultimately the v8 gamble enables a class of JS to run extremely well.1 reply 1 retweet 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror unfortunately expressing some systems (like large web apps) in a way that works well for v8 is tricky1 reply 0 retweets 2 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror largely because of the gamble it places. When it looses, it really looses1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror conversely JSC has been working hard to improve perf without making risky assumptions about the code1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror the good news is, we have been working with the v8 team. They have made some good progress, and...1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror are continue down that path. At the same time, we continue to work to both reduce the work ember does and...1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror and massage embers internals to mitigate the cliffs.1 reply 0 retweets 0 likes -
Replying to @stefanpenner
@onemandesignarm
@codinghorror some of the work on our side is frustrating because the contortions required are unfortunate.2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner @onemandesignarm we detect android and send down half the content, this cuts performance loss in half, at cost of pages2 replies 0 retweets 3 likes
@codinghorror @stefanpenner @onemandesignarm Discourse runs twice as fast on Android. Confirmed! :trollface:
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.