3 ms·
For me, the big thing Firefox needs is better power management. Mac user here, and streaming video or doing a video call just kills my battery compared to Chro
by dbg31415 2y ago
For me, the big thing Firefox needs is better power management.
Mac user here, and streaming video or doing a video call just kills my battery compared to Chrome or Safari.
Would love to see more focus on energy consumption optimization.
- yjftsjthsd-h 2y ago> Mac user here, and streaming video or doing a video call just kills my battery compared to Chrome or Safari. Is it not using hardware acceleration or something?
- stqism 2y agoProbably need to check on this, but I’ve heard of issues around video decode and Firefox.
- switch007 2y agoIs this a comment from 2018? I thought FF on MacOS was pretty good these days. And are you suggesting Chrome is similar to Safari in terms of power usage? That would surprise me Safari will of course always be better. It's no competition
- dsego 2y agoMy experience as well, it used to be bad, it's okay now.
- dbg31415 2y agoI don't actively monitor it every day, but I feel it! Intel MacBook from 2021. My laptop gets so hot when running Firefox -- almost instantly (certainly after 3-4 minutes). But I can do a call for an hour on Chrome and it doesn't get nearly as warm. And the battery just drops accordingly as the fans struggle to keep up. I like to use Firefox, but I end up doing all my calls when I'm not plugged in on Chrome as a result of the power use / heating issues.
- e44858 2y agoIt's the opposite for me on Linux. Firefox can play 4k 60fps perfectly, while Chrome drops frames and gets hot. I guess hardware-accelerated video is hard to get right.
- cassianoleal 2y agoMac user here as well. Chrome kills my laptop (though I've uninstalled it about a year ago and never looked back). Firefox is pretty good. Safari is better, at least in terms of power management. Firefox is my main browser, and it's a beast. Very low footprint, snappy and very decent in terms of power consumption.
- finack 2y agoCould it actually be the hundreds of megabytes of JavaScript each website insists on executing?