I gave up using Chrome a decade ago. It’s a power sucking pig. Safari has its own issues, but at least it’s usable. When I need something that isn’t Safari, I use Firefox.
I gave up using Chrome a decade ago. It’s a power sucking pig. Safari has its own issues, but at least it’s usable. When I need something that isn’t Safari, I use Firefox.
Chrome has used less power than Safari for a few years now. As far as I know, the only good reason to use Safari is to use FairPlay DRM for sites that need it. For all other purposes, Firefox or Chrome is superior. https://birchtree.me/blog/everyone-says-chrome-devastates-ma...
Interesting, thanks. I’ll give it another try. It certainly used to be a pig. I remember times when the fan on my MacBook sounded like a freaking hovercraft and you’d go into system monitor and see a Chrome process just sucking down every CPU cycle. You’d quit Chrome and the fans would spin down and stop. But if they’ve fixed that, maybe it’s worth another go.
Safari has a terrible developer experience and has been behind in implementing the various browser API for years, including AV1 support.
Like I said, Safari has its own issues. But huge power consumption isn’t one of them.
Safari has had AV1 support for a long time. Absolute majority of "various browser API" that they don't support are all kinds of "Web Bluetooth"-like crap that I don't need and which only introduces attack and tracking surface when supported.