Re:JavaScript performance, WebAssembly, and Shared Memory in...
by ng12 on Thursday April 20, 2017 @08:19PM
(#14162064)
That's not even in the same league as either of the Firefox issues I've referenced. The first is actually app-breaking (in our case users couldn't see any of the select options) the second is just plain IE-level of stubbornness. I'm not saying Chrome is perfectly immaculate, just trying to explain why it's so popular among the dev community in a way FF/IE are not.
[ Parent
| on HN ]
There are no comments on this comment yet.