This. Apparently, we're still waiting for a Therac-class incident before "don't mess with critical infrastructure for what seems harmless fun to you" will even register on the radar with the "move fast and break other people's things" crowd.
That story, uh. If you cut off the last couple sentences it would be somewhat convincing. In its entirety it just suggests a very broken process. Where an automatic extension invalidates firefox, but renaming chrome.exe to firefox doesn't invalidate firefox!?
Perhaps Chrome is also supported by the testing infrastructure, but they chose to use only firefox?
Or, they have multiple scripts running in the background which assume there is a `firefox` process. In such a case the smallest (and quickest) change is to rename the binary.
Incredible. Mozilla really screwed up on this one.