Hacker News new | ask | show | jobs
by Xolvixica 2209 days ago
Unfortunately I have to disagree with even that. Firefox (the default browser in most Linux distros) can't do hardware accelerated video, so you tend to get tearing/stuttering or at the very least a higher CPU load when watching YouTube for example, compared to say Windows, resulting in increased battery consumption if a laptop or at the very least increase fan speeds.

I know it's being worked on with Firefox having acceleration worked on in Wayland, but right now, if even the simplest and most common use-cases have major downsides compared to Windows/OS X, it's hard to justify moving to a worse experience. Windows rules with vendor support, that's just how it is. I've grown tired of having to compromise.

3 comments

> Firefox (the default browser in most Linux distros) can't do hardware accelerated video

https://wiki.archlinux.org/index.php/Firefox#Hardware_video_...

In short: Firefox supports it under Wayland since version 75 (and for more formats since 76).

Not that I've really noticed this being an issue under X11.

AFAIK OSX hides from userland the support for VP9 decode acceleration present in the Macbook's hardware, Youtube's primary codec these days, so now Firefox supports VAAPI under Wayland it is already ahead of OSX/Macbooks in this regard.
I need to test this (I didn't know about the hardware acceleration), however, first: tearing and stuttering are different things.

Tearing required, for a very long time, to be configured manually in the Xorg configuration. However, on 20.04 now it's not needed anymore (I don't know why; I've just verified it on Nvidia and Intel GPUs).