(On that note, many complaints about Safari I hear from developers fall on my ears as "I don't care about web compatibility!" as it has never NOT been the case on the web that you need to care about feature support and resource management.)
I can assure you, this is still true. I use Chrome when plugged in at my desk and Safari for everything else on the go. Chrome still isn't great on memory or battery life.
It's even more obvious when watching video where safari will be 5 to 10 points lower than Firefox.
Harder to say when it's rendering page but the fact of the matter is that I tried both for years, Firefox always drain the battery faster.
Safari uses macOS for video so the points will be on macOS. Firefox uses it own internal video decoder. That is why image and video codec support on Safari is dependent on macOS upgrade not Safari.
I mean, observably, this is still the case.
Now, luckily the M-series laptops have such insane battery life that it barely matters compared to before... but I can still observe about an hour of battery life difference between Safari and Chrome on an M2 Macbook Air (running Sequoia). Now, my battery life is still in the region of 7.5 hours, so even if it's a large difference it's not impacting my workday yet (though the battery is at 90% max design capacity from wear).
I know this, because there are days where I only use chrome, and days where I only use Safari, and I do roughly the same work on each of those days.
Safari loses out when you run with a lot of Tabs. Both Chrome and Firefox knows when to unload tabs. ( Firefox even have about:unloads to tell you the order of Tabs it will unload! )
Try opening Tab Overview in Safari and it will start loading all the website for thumbnails, paging out to disk due to low memory, writing hundreds of GB to page. It also put Tabs on low running priority in the background rather than pausing them like Firefox or Chrome. ( Not sure if that is still the case with Safari 26, at least it was with 18 ). To combat that, restarting the browser time to time helps.
Safari is well tuned for iOS as a single tab, single page usage. On MacOS when doing many tabs it start to get slow and inefficient. And this is very much a Safari issue not an Webkit issue because Orion is a lot better at it.
And yes I have filed Radar report for many of the issues but I have come to the conclusion Apple doesn't care about multi tab usage on desktop Safari.
Uhh, not my experience. I default any video watching longer than a short clip to safari. It is still the best browser for video IME.
Since its birth, Firefox is still the only browser that manage multiple ( hundreds or in some cases, thousands! [1] ) tabs better than any browser. And in my view in the past 12 - 24 months Firefox has managed to be as fast as chrome. While Chrome also improved on its multiple Tab browsing experience.
Safari.... I dont know why this battery life argument keeps coming up because it is not the case. It hasn't been so for at least 5 - 6 years.
Mozilla could have played the trust angle when they have the good will and money. They could have invested into SaaS that provides better revenue generations other than getting it from Google. They could also have partnered with Wikipedia before they got rotten. But now I am not even sure if they still have the "trust" card anymore. Gekco is still hard to be embedded, XULRunner could have been Electron. They will need to get into survival mode and think about what is next.
[1] https://www.tomshardware.com/software/mozilla-firefox/firefo...