Earlier quoted context omitted.
I take offense to someone calling me a liar. Try typing this into a JS Console: var xx = []; xx[30000000]=42; var yy = xx.slice(0); It took almost a week to track down this problem where FF was taking 13 seconds to startup. We've spent a lot of time working on this and it is always in the cards to support this on all the other browsers. We've fixed tons of bugs and have gotten closer to it working the way it should,…
> Try typing this into a JS Console: var xx = []; xx[30000000]=42; var yy = xx.slice(0); What specific problems does this create that prevents you from shipping with a degraded experience? Or feature detect this problem and serve some type of notice. If bleeding-edge Chrome is the only browser good enough for this site then it's a problem with the site's architecture. > Any insinuation that this is an attempt to sell…
It's not just a degraded experience as in 'turn off this feature', the bug in question affects the entire infrastructure of how the app works, since it is part of the message passing and serialization mechanism used. It's legal, standard, JS, that just happens to run slow.
In this case, a workaround is available, and it is already fixed, but not shipped, because we froze commits some time ago for launch.
> That's either a lie or incredibly naive. You wouldn't have shipped without iOS. Full-stop.
You mean like we didn't ship support for Android tablets? You would have thought with the big Android Lollipop and Nexus 9 launch, we would have made sure this worked there, right?
Maybe you should think about Hanlon's Razor as an explanation.