3 ms·

Still, I suspect Google’s developers are too focused on development in Chrome-only. If true, this may have contributed to perf issues arising in Firefox, in the

• Kalium 12y ago
  Did you read the clearly documented technical details? Basically, array slicing on sparse arrays in Firefox is much, much slower than on Chrome. It's not a matter of lacking competence or skills or anything of the sort. It's a basic question of what level of resources you are willing to put into a product before you have something to beta-test. Inevitably, that's less than the amount required to be perfect in every aspect.
  • bzbarsky 12y ago
    > array slicing on sparse arrays in Firefox is much, much slower You mean "was", since it's fixed? > It's not a matter of lacking competence or skills or anything of the sort. Yes, it is. Not reporting a bug when you run into it but instead just complaining about it is in fact lack of competence. Arguably using super-sparse arrays in JS is also lack of competence, but the other is much more obvuous. > It's a basic question of what level of resources you are willing to put in Filing a bug takes about 5 minutes.