@codinghorror what we need to do is run octane/sunspider etc across ARM devices and browsers and show JSC smoking v8. They respond to that.
-
-
Replying to @wycats
@wycats@codinghorror Why do you guys think this is a V8 problem and not a Blink problem? Genuinely can't find any evidence of that.4 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@wycats I see you updated the bug; where's the evidence of a Blink problem? https://code.google.com/p/v8/issues/detail?id=2935 …1 reply 0 retweets 0 likes -
Replying to @codinghorror
@codinghorror@wycats For web apps layout/rendering is usually slower than JS execution so I put the burden of proof the other way around.2 replies 0 retweets 0 likes -
Replying to @codinghorror
@codinghorror@wycats That's a good point; very interesting.2 replies 0 retweets 1 like
@domenic @codinghorror that's what I was getting at with iOS. JITs are also where the massive arch differences lie and this is ARM-specific
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.