wfh

wfh, 1 year ago (edited 1 year ago)

Counter-counterpoint: Wayland is perfectly fine and production ready and has been for several years now, as long as you’re on AMD or Intel GPUs. The nVidia drivers are still undercooked and not ready for proper daily use.

wfh, 1 year ago

Still, 100% nVidia’s fault, not Wayland.

No offense, but your argument is exactly like “electric cars are still undercooked and not ready for proper daily use because I still have to put gasoline in mine and can’t afford one”.

wfh, 1 year ago

Feature parity with X has never been the goal. Because most of X’s features are a legacy of the 80’ and dreadfully obsolete anyway.

I’m all for maintaining compatibility where it makes sense, but carrying over a 40 years old feature set just in case is the best way to prevent anything from moving forward.

Wayland can already do or is actively being developed for stuff that is relevant to modern systems: multi-monitor with different refresh rates and scaling, HDR etc. Stuff that X would never dream of.

wfh, 1 year ago

I don’t think it’s heresy, but I always find it funny that an extremely vocal community shits on systemd for being a bloated tentacular monster shat should be abandoned, but praise X for being a bloated tentacular monster.

In a way, Wayland is much closer to the Unix Philosophy than X. It’s a display protocol, nothing more. Everything else should be implemented by the applications using this protocol. X has grown over the decades to include way too many features and edge cases.

Translation layers like XWayland are important and extremely useful for the transition period, but shouldn’t be taken as a sign that Wayland is not ready for prime time. If 10% the people shitting on Wayland had instead worked on adding Wayland functionality to their favorite apps (that includes you fuckers at nVidia), the transition would have ended years ago.

wfh, 1 year ago

SO. MANY. STAR. TREK. MEMES.