A Google engineer would have no incentives to kill Firefox unless he can convince a promo committee that killing Firefox is good for Google, so I am not sure wh

A Google engineer would have no incentives to kill Firefox unless he can convince a promo committee that killing Firefox is good for Google, so I am not sure why anyone would do it. I mean, do you think someone would put "Slowed down Firefox gmail page load by 50%." on their promo packet? So for it to be done in secret for many years you would need someone with enough clout to circumvent the promo process behind it. I am not sure how high up you need to be to do that, or if it is even possible to do for engineers. Instead if you take the promo driven perspective, it is a lot easier to make things work well in a single browser. So the engineer makes a site twice as faster in Chrome, writes "Made the site twice as fast" in their promo packet and gets promoted. No need to mention that Firefox performance got worse after the fix, the promo committee wont have time to check that.