I don't think you can make a blanket statement like this. My experience has been almost the opposite, Chrome always uses significantly more CPU for me.
I think it really depends on hardware, drivers etc.
Really? Firefox works fine with netflix on my pop_os laptop.
GP is talking about aarch64 Linux laptops, and IIUC Pop_OS uses x86_64.
The key is `aarch64` ;)
Re:Firefox Was Always Enough
by AsyncAwait on Wednesday December 16, 2020 @02:00PM
(#25446822)
Opposite experience. For starters, Chromium doesn't even support video hardware decoding on Wayland properly.
That's unfair. Not even Emacs master works under Wayland. It's nowhere near a replacement for X.
Re:Firefox Was Always Enough
by AsyncAwait on Wednesday December 16, 2020 @05:23PM
(#25449609)
> It's nowhere near a replacement for X.
It is for me and many others. Emacs works great under XWayland but Chromium HW video acceleration doesn't.
Emacs is a community project whereas Chromium has billions poured into it. Even Wine's getting Wayland support now and that ran under XWayland fine.
I don't think it's that unfair. Firefox on Linux is just better. Leaves some to be desired, sure, but a lot less than Chromium.
On my aarch64 devices, Chromium in a Docker image loads faster, never dominates the CPU, renders video and websites faster, and has working DRM. Firefox is slower in every respect and can't render Netflix.