> A massive subset of Firefox devs are Linux users. No, they are not. A massive subset of Firefox devs are Apple users. For Linux, the occasional Redhat or SuS

> A massive subset of Firefox devs are Linux users. No, they are not. A massive subset of Firefox devs are Apple users. For Linux, the occasional Redhat or SuSE dev does the most-needed fixing. > Those features are missing largely because they are hard to implement reliably on Linux and customers (who are largely not Linux users) won't feel the impact. Neither of these are true. It does make easier rationalizing Linux mistreatment, though. If there was no impact, the equivalent functionality would not be needed to be implemented under other OS-es either. You have bugzilla full of feedback, that it does have an impact. It also makes Linux itself look worse, compared to other systems. > There are often flags you can set to try and use them on Linux, YMMV. I know, that you can force OMTC, for example. I've been doing that for years, with zero bugs. Why can't Mozilla do that by default? They haven't reviewed the situation for years, that's how much they care. Also, for example, the EGL situation (needed for Wayland, obviously Wayland apps cannot use GLX without X11) was purely Firefox problem, not the driver stack one. (Worked on by Redhat dev). > If you try doing much hardware graphics (let alone game development) for Linux end-users you'll understand why features like OMTP or OMTC are late to ship on that platform, if ever. Mesa is one of best of breed drivers, especially compared to some drivers you can find on other platforms. See here: https://code.blender.org/2019/04/supported-gpus-in-blender-2-80/ https://code.blender.org/2019/04/supported-gpus-in-blender-2... for what Blender devs think about the driver situation. > Even on Windows some new stuff like WebRender has to be manually opted in on specific driver versions and architectures one at a time, because it turns out video drivers are really bad and if you ship early your app will crash. I'm fine with incremental enablement. I'm not fine with the enablement never arriving. And again; the original post was about the irony of the situation Firefox itself finds themselves in; exactly the same excuses are used against them.