News for hackers. Stuff that matters.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by dist-epoch on Monday April 10, 2023 @03:22PM (#35516261)
> That's 250 megawatts saved, the equivalent of an average coal power plant. Because some Microsoft engineer missed a bug.

Are you sure you want to invoke this logic? Because following it through imagine the energy savings if Firefox users switched to Chrome.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by LeoPanthera on Monday April 10, 2023 @03:38PM (#35516445)
> Are you sure you want to invoke this logic? Because following it through imagine the energy savings if Firefox users switched to Chrome.

Ironically, Mac users routinely complain about how power-hungry Chrome is on the Mac. Safari is significantly more efficient.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by ChuckNorris89 on Monday April 10, 2023 @03:52PM (#35516615)
>Safari is significantly more efficient.

Based on the increased laptop battery life I notice, so is using Edge on Windows.

It makes sense that both Apple and Microsoft can extract the best out of their OS + browser. There's no way Firefox can compete on such OS specific optimizations.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by 908B64B197 on Monday April 10, 2023 @07:40PM (#35518791)
> so is using Edge on Windows.

The new Edge based on Chromium performs better than Chrome with regards to power consumptions.

The old Edge was even better in terms of power consumption. Like a few extra hours of battery life.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by gorby91 on Monday April 10, 2023 @09:52PM (#35519724)
To continue to overextend the analogy though, that's asking people to use Edge over Chrome or Firefox is like trying to market the Smart Car. Few people want to be seen driving it, fuel efficiency be damned.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by BizarroLand on Tuesday April 11, 2023 @07:05PM (#35532909)
And no browser is more efficient that simply turning off your computer and reading by daylight.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by Karunamon on Monday April 10, 2023 @04:40PM (#35517138)
* * *
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by dijit on Monday April 10, 2023 @05:06PM (#35517411)
Its been a really long time but safari on Windows was a thing and it did run a lot leaner in the background than anything else available at the time (except Opera if memory serves).

It’s entirely possible that Safari is intentionally avoiding features that make it wake up-

I doubt that it does anything unavailable to other browsers, thats MS territory, because they wanted features. I feel like safari, by contrast, doesn't want to add features.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by LeoPanthera on Monday April 10, 2023 @05:56PM (#35517870)
It's not impossible, but I doubt it, if only because very few third party applications use as much as Chrome does. The only exceptions are things that actively use a lot of CPU, like compilers or compressors.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by jeron on Monday April 10, 2023 @06:28PM (#35518152)
Blessed or not, I still end up using Safari. The improvement in battery life is too significant to ignore
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by gnicholas on Monday April 10, 2023 @11:27PM (#35520413)
Have you compared versus Orion, which is also based on WebKit (and can run most Chrome and Firefox extensions)?

IME, Safari is no better than Brave in terms of battery, even when I’ve got hundreds of tabs open.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by drdrey on Monday April 10, 2023 @06:32PM (#35518187)
That's because optimizing for battery life is a stated goal of the Safari team, it's actively benchmarked
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by ojosilva on Monday April 10, 2023 @06:50PM (#35518344)
Totally guesswork here, but I'd say Chrome has a lot more telemetry, profiling and tracking built-in and its users tend to use a lot more plugins, including things like ad-blockers that scan over each webpage and can be beneficial (battery-wise) or not depending on content. Safari users are more of a barefoot type. A power user is more likely to not be running Safari. And a power user may, well, prefer to sacrifice battery power to get the power they seek.

Besides, there's some precedent set in 1998 by a certain OS that "favored" their embedded browser over the competition, so I doubt Apple would want to tickle that fancy.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by tshaddox on Monday April 10, 2023 @08:53PM (#35519303)
I would be at least slightly surprised if Apple would deliberately hold back power-saving techniques from third party developers. It’s not like this is something that makes Safari much more appealing to users. Most users wouldn’t even notice that their choice to use Safari is responsible for their great battery life.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by scarface74 on Monday April 10, 2023 @09:24PM (#35519519)
Third party developers are free to go here and see what Apple is doing:

https://github.com/WebKit/WebKit

> Most users wouldn’t even notice that their choice to use Safari is responsible for their great battery life.

Seeing that MacOS has called out which apps are using the most energy for years, users can definitely tell which apps are using the most battery life.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by saagarjha on Monday April 10, 2023 @10:20PM (#35519945)
Apple can and does leave things out of that repo.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by scarface74 on Monday April 10, 2023 @11:23PM (#35520378)
So you think there is a conspiracy by Apple to not allow third parties to be battery efficient and make there hardware look bad?

But you are free to download the source code, compile and run it yourself to see if it is less battery efficient than the official builds.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by saagarjha on Tuesday April 11, 2023 @12:01AM (#35520661)
I did not say that.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by Karunamon on Friday April 14, 2023 @07:55AM (#35568440)
I absolutely think there is a conspiracy (inasmuch as "conspiracy" can be defined as "not going out of their way to change it") to make the competitors to Apple applications look worse than their own offerings. It does not reflect poorly on Apple when Firefox performs worse and uses more memory and battery than Safari.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by scarface74 on Friday April 14, 2023 @10:48AM (#35570164)
How is Apple suppose to change Firefox and Chrome’s source code?

If either browser’s manufacturer wants to see what Apple does to make Safari more battery efficient, they are free to look at the source code to WebKit.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by Karunamon on Saturday April 15, 2023 @11:05AM (#35581263)
And as the other person told you already, Safari.app is not what you get if you build the WebKit source. In much the same way that you can't judge Chrome by Chromium, one is the base of the other, not the whole.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by scarface74 on Monday April 10, 2023 @09:20PM (#35519492)
If only the underlying engine were open source so people could see what “secret APIs” (sic) it was using…
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by saagarjha on Monday April 10, 2023 @10:20PM (#35519951)
It’s mostly that they care. Chrome is designed with the mindset that it’s the most important thing running on your computer.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by HWR_14 on Monday April 10, 2023 @10:48PM (#35520136)
If I had to guess, it's that Apple refuses to implement very CPU-heavy JS features they don't think add much value in Safari.

I recall some feature I was using that ran in an inferior way to save power on Safari, so much so that I had to kill that feature and use a different API

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by TheKarateKid on Tuesday April 11, 2023 @11:38AM (#35526656)
I think it's more that Apple implements power saving behavior into the JS engine on desktop much like they do on mobile. For example, pausing background scripts on inactive tabs and disallowing autoplay on videos even on desktop.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by gnicholas on Monday April 10, 2023 @11:23PM (#35520382)
I’ve not noticed a difference between safari and brave, so I’d say the former is not blessed.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by TheKarateKid on Tuesday April 11, 2023 @11:34AM (#35526601)
It's because of the quality of Chrome. Google's focus is on features and security, with efficiency secondary. Safari's primary focus is efficiency.

Google's only incentive to make Chrome more efficient is when they start receiving heat (no pun intended) about bad performance.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by funcDropShadow on Wednesday April 12, 2023 @03:36AM (#35536196)
Googles focus is to collect as much data about the user as possible, nothing else.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by axolotlgod on Monday April 10, 2023 @03:29PM (#35516353)
Does Chrome really use significantly less resources than Firefox? Are there numbers there?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by IntelMiner on Monday April 10, 2023 @03:32PM (#35516377)
It took a lot longer for Firefox to get GPU accelerated video playback on Linux iirc

Perhaps a "niche" use case for some, but there's a lot more Firefox users on Linux in particular

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by tristan957 on Tuesday April 11, 2023 @11:32AM (#35526560)
Isn't Chromium hardware acceleration currently broken on Linux?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by haupt on Monday April 10, 2023 @05:36PM (#35517700)
According to Tom's Guide[1] Microsoft Edge beats out both when it comes to RAM utilization but Chrome just edges out Firefox when loading >10 tabs. That was in 2021. I'd be interested to see any other comparisons or benchmarks.

1. https://www.tomsguide.com/news/chrome-firefox-edge-ram-compa...

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by prmoustache on Monday April 10, 2023 @06:04PM (#35517951)
This is with no extensions installed right?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by ChuckNorris89 on Monday April 10, 2023 @03:38PM (#35516450)
Or the energy used by all the electron apps on all operation systems.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by airza on Monday April 10, 2023 @03:43PM (#35516508)
There are good reasons to not use chrome over firefox, but few reasons to leave firefox bugged. I don’t think the same utilitarian logic applies.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by throwbadubadu on Monday April 10, 2023 @04:54PM (#35517273)
Yeah, finally as the market share is where it should be for Firefox Microsoft had no more reasons to leave it on :D
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by omneity on Monday April 10, 2023 @03:44PM (#35516516)
It's not too bad an analogy. Think of it this way:

- Switching from Firefox to Chrome might be similar to switching between two car models, one consuming less energy than the other.

- Fixing this bug is more like going to a car workshop to fix an injector issue in your car that was causing higher fuel consumption and more pollutants.

The first one is really a matter of tradeoffs and personal choices. The second one is less of a choice and more of an actual issue that was left due to negligence. Hardly similar.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by sgtnoodle on Monday April 10, 2023 @04:51PM (#35517244)
Isn't it more like an auto maker issuing a recall to fix an injector issue in all their cars?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by omneity on Monday April 10, 2023 @05:02PM (#35517380)
An 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.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by sgtnoodle on Monday April 10, 2023 @05:08PM (#35517431)
A 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.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by jmspring on Monday April 10, 2023 @08:52PM (#35519294)
With 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).
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by robotresearcher on Monday April 10, 2023 @10:23PM (#35519978)
The article is about Firefox. It’s right there.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by deafpolygon on Tuesday April 11, 2023 @12:05AM (#35520689)
What's wrong with Chrysler?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by wolrah on Monday April 10, 2023 @09:52PM (#35519732)
> 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.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by lotsofpulp on Monday April 10, 2023 @03:53PM (#35516632)
The cause and effect exists whether or not some commenter on HN writes about it.

The reason it is not “invoked” is because energy prices are sufficiently low (due to not pricing in externalities) that there exists little incentive for end users to optimize for power usage.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by gruez on Monday April 10, 2023 @04:39PM (#35517118)
>The reason it is not “invoked” is because energy prices are sufficiently low (due to not pricing in externalities) that there exists little incentive for end users to optimize for power usage.

You're right in principle, but in practice even factoring in externalities electricity prices won't be high enough for people to care. Using current US carbon intensity for electricity generation[1] and the higher end estimates for the social cost of carbon[2] gets us carbon costs of $0.142 per kWh. The average prices in US is $0.168. Adding in carbon costs would almost double the price, but there are countries with even higher electricity prices[4] and they're not exactly switching to more efficient software in droves to save energy.

[1] https://emissionsindex.org/

[2] https://en.wikipedia.org/wiki/Social_cost_of_carbon#Carbon_p...

[3] https://www.bls.gov/regions/midwest/data/averageenergyprices...

[4] https://www.statista.com/statistics/263492/electricity-price...

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by robotresearcher on Monday April 10, 2023 @10:29PM (#35520018)
Battery powered devices have battery life as the dominant user-sensible cost rather than the price of electricity.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by lkbm on Monday April 10, 2023 @04:11PM (#35516838)
I mean, sure, I could also just turn off my computer. Presumably people use Firefox for a reason, and making that a option use less energy is pure upside, and it's very interesting to see how big of an upside it might be.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by volkk on Monday April 10, 2023 @04:22PM (#35516937)
> Because following it through imagine the energy savings if Firefox users switched to Chrome

i've read everywhere that Firefox at this point is far more energy efficient than Chrome...is that not true?

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by Georgelemental on Monday April 10, 2023 @04:33PM (#35517059)
If one user switches to Chrome, the energy savings are only for that one user. If one Microsoft engineer fixes a bug, the energy savings are for the many thousands who use Firefox on up-to-date Windows.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by kramerger on Monday April 10, 2023 @04:41PM (#35517144)
> imagine the energy savings if Firefox users switched to Chrome.

Nah, I like my privacy. How about replacing Electron apps with native apps instead?

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by ouid on Monday April 10, 2023 @04:44PM (#35517171)
Using firefox without memory errors is a pareto optimization over using firefox with memory errors.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by tgv on Monday April 10, 2023 @05:00PM (#35517356)
Think more like this: this bug cost an average coal power plant, all other things being equal. I doubt it's that much, but it certainly did waste a lot of energy.

> imagine the energy savings if Firefox users switched to Chrome.

Imagine the privacy savings if Chrome users switched to Firefox.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by shapefrog on Monday April 10, 2023 @05:07PM (#35517419)
> imagine the energy savings if Firefox users switched to Chrome

This is why I left firefox.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by tyingq on Monday April 10, 2023 @05:08PM (#35517430)
Maybe compare manifest v2 friendly Firefox with uBlock Origin vs eventual Chrome without it :)
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by revolvingocelot on Monday April 10, 2023 @05:17PM (#35517506)
Serious savings indeed when the Javascript cryptominer some ad network blithely serves up is ad-blocker'd, but we prefer synthetic benchmarks.

In seriousness, though, this is an issue. Elsewhere, I observe arguments about eg userbenchmark rankings, and the comparative relevance of single-core vs multicore performance. Are you playing a game, or rendering video 24/7 -- or running some entirely synthetic workload that allows for a peak performance the real world would never achieve? Same kinda problem.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by rahmeero on Monday April 10, 2023 @07:41PM (#35518798)
Not sure if this is related, but Chrome on my Macbook regularly gets to a state where one process (a tab?) is consuming 4 Gb RAM and 20%+ CPU. This happens on both M1 and Intel CPUs, on multiple releases of OS.

Situation seems to happen some time after visiting ad-heavy sites (yeah I know I should install an ad-blocker). Have others noticed this? Seems to be Chrome. I also use Firefox and occasionally Safari but have not noticed that with those browsers.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by saagarjha on Monday April 10, 2023 @10:22PM (#35519970)
Web browser benchmarks are typically designed to track real-world applications
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by xxs on Monday April 10, 2023 @05:13PM (#35517474)
>Firefox users switched to Chrome.

Far worse due to privacy/adblock addons.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by wiseowise on Monday April 10, 2023 @05:14PM (#35517482)
> Because following it through imagine the energy savings if Firefox users switched to Chrome.

Enlighten us.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by harry8 on Monday April 10, 2023 @05:40PM (#35517726)
Imagine the power savings if chrome users switched to lynx.

Imagine the power savings if everyone used pihole, ublock etc.

Second uses more power than the first and is better. Do it!

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by hanoz on Monday April 10, 2023 @06:37PM (#35518236)
> imagine the energy savings if Firefox users switched to Chrome.

Imagine the energy squandered on all the extra goods and services bought by users using a browser owned by an advertising company, instead of Firefox.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by everdrive on Monday April 10, 2023 @07:58PM (#35518936)
Now do one for javascript.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by mr_toad on Monday April 10, 2023 @08:10PM (#35519026)
> Are you sure you want to invoke this logic? Because following it through imagine the energy savings if Firefox users switched to Chrome.

And then imagine Safari on an M1.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by viraptor on Monday April 10, 2023 @09:54PM (#35519742)
It works for a single case, but not sure about long term. We still have at least a little bit of competition. All browsers improve because the other ones improve. If we all switched to Chrome or Safari because of the power saving, we'd just get another version of IE monopoly/stagnation which could result in more power wasted longterm.

The optimum is likely somewhere where most people use the currently most efficient solution and others keep alternatives alive and competitive.

Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by midoridensha on Monday April 10, 2023 @10:25PM (#35519994)
Imagine the energy savings if all users installed a good ad-blocker.
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by michaelcampbell on Tuesday April 11, 2023 @07:44AM (#35523720)
How many megawatts saved if everyone learned how to do all their work on text-only consoles running linux?
Re:Microsoft fixes 5-year-old Defender bug, reducing Firefox... by rhaway84773 on Wednesday April 12, 2023 @05:25AM (#35536979)
Those are 2 very different things.

In switching browsers, you get different features, workflows and functionality, many of which you prefer on Firefox, which is why you’re using it.

With this bug fix, there is absolutely no loss or change in functionality (other than increased battery life), and yet you’re getting the benefits.

This bug is pure waste.