3 ms·
Isn't it more like an auto maker issuing a recall to fix an injector issue in all their cars?
by sgtnoodle 4y ago
Isn't it more like an auto maker issuing a recall to fix an injector issue in all their cars?
- omneity 4y agoAn analogy can only get you so far, but in this case the bug is caused by Microsoft Defender, yet Firefox, the car manufacturer, is a different entity. So I wouldn't call it a recall.
- sgtnoodle 4y agoA bunch of cars across many manufacturers were recalled in the 2010's due to a defect in the airbags made by the same manufacturer. One could also argue that the OS is the car, the browser is the chauffeur, and the user is the passenger.
- jmspring 4y agoWith regard to browsers, I think we need more manufacturers, not just the GM (Google/Chrome) of browsers. I want Ford in there as well. (Sticking with US automotive companies).
- deleted 4y ago[deleted]
- deafpolygon 4y agoWhat's wrong with Chrysler?
- wolrah 4y ago> but in this case the bug is caused by Microsoft Defender, yet Firefox, the car manufacturer, is a different entity. Quoting the Mozilla engineer responsible for most of the recent activity on the bug: "This problem has two sides: Microsoft was doing a lot of useless computations upon each event; and we are generating a lot of events. The combination is explosive. Now that Microsoft has done their part of the job, we need to reduce our dependency to VirtualProtect." It was also noted elsewhere in the thread that similar, though less severe, CPU impact is seen with other antivirus products. Microsoft was doing something wrong that made this operation more expensive than it needed to be, but Mozilla is also doing this far more than any other browser.