Some JS features are faster on Chrome and some on Firefox. Additionally, while Firefox is killing it on CSS and some layout stuff with Stylo and WebRender, JS is the area where Firefox isn't dominating.
It's trivial to explain the speed difference without assuming it intentional. In Inbox's case, sparse arrays were an issue initially[0] (and like many of the perf issues, it's been fixed[1].)
There will always be perf trade-offs. If you find any where they chose X over Y when X and Y are equal on Chrome, and X is faster than Y on Firefox, then let's talk about anti-competitive behavior.
It's trivial to explain the speed difference without assuming it intentional. In Inbox's case, sparse arrays were an issue initially[0] (and like many of the perf issues, it's been fixed[1].)
There will always be perf trade-offs. If you find any where they chose X over Y when X and Y are equal on Chrome, and X is faster than Y on Firefox, then let's talk about anti-competitive behavior.
[0] https://qht.co/item?id=8495498 [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1087963