Re:Firefox is on a slippery slope
by jimktrains2 on Sunday December 17, 2017 @09:21AM
(#15945834)
It has also already caused economic damage as well as waisting a lot of people's time. https://reddit.com/r/talesfromtechsupport/comments/7k7wum/wh...
[ Parent
| on HN ]
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.
Re:Firefox is on a slippery slope
by Dylan16807 on Sunday December 17, 2017 @02:32PM
(#15947227)
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!?
Re:Firefox is on a slippery slope
by nallerooth on Monday December 18, 2017 @05:26AM
(#15950677)
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.
Re:Firefox is on a slippery slope
by jimktrains2 on Monday December 18, 2017 @01:39AM
(#15949901)
Perhaps Chrome is also supported by the testing infrastructure, but they chose to use only firefox?