Hello, Linux Developer
-
wrote on last edited by [email protected]
Not sure how this applies when:
- X11 was the only standard prior to Wayland.
- GNOME is dropping X11 in a short time.
- KDE's telemetry even five months ago showed 80+% of (that portion of) their userbase uses Wayland, and they plan to drop X11 once they have a concrete set of problems worked out.
- Hyprland and Sway run Wayland exclusively.
- Cinnamon, MATE, and Xfce are working on Wayland sessions. Cinnamon's is there but, I think, still experimental.
- Budgie is working to go Wayland-only.
- There's no sign that Wayland will stop improving from a state that's arguably already much better than X11.
- X11's actual maintainers barely want anything to do with it beyond bug fixes, and the only person who wants to "innovate" it via a fork is a bigot and a fucking moron who doesn't know things you learn in CS 101.
- X11's maintainers are majorly involved in developing Wayland and have been since the start. This is their idea.
It seems like it went from "Situation: there is one standard" to "Situation: there are two standards developed by largely the same people with one set to replace the other", and then soon: "Situation: there is one standard and one translation layer kept around for a decade or so for compatibility."
Not every single time someone tries to make things better is this xkcd relevant; this had nothing to do with unifying standards and everything to do with superseding one.
-
Not sure how this applies when:
- X11 was the only standard prior to Wayland.
- GNOME is dropping X11 in a short time.
- KDE's telemetry even five months ago showed 80+% of (that portion of) their userbase uses Wayland, and they plan to drop X11 once they have a concrete set of problems worked out.
- Hyprland and Sway run Wayland exclusively.
- Cinnamon, MATE, and Xfce are working on Wayland sessions. Cinnamon's is there but, I think, still experimental.
- Budgie is working to go Wayland-only.
- There's no sign that Wayland will stop improving from a state that's arguably already much better than X11.
- X11's actual maintainers barely want anything to do with it beyond bug fixes, and the only person who wants to "innovate" it via a fork is a bigot and a fucking moron who doesn't know things you learn in CS 101.
- X11's maintainers are majorly involved in developing Wayland and have been since the start. This is their idea.
It seems like it went from "Situation: there is one standard" to "Situation: there are two standards developed by largely the same people with one set to replace the other", and then soon: "Situation: there is one standard and one translation layer kept around for a decade or so for compatibility."
Not every single time someone tries to make things better is this xkcd relevant; this had nothing to do with unifying standards and everything to do with superseding one.
Huh neat. I kinda just assumed "wheel11" had 10 other versions and didnt realize it was an analogy for something irl
-
Huh neat. I kinda just assumed "wheel11" had 10 other versions and didnt realize it was an analogy for something irl
wrote on last edited by [email protected]You are actually correct that Wheel11 had 10 other versions. It just happens that those 10 other versions were released before September 1987.
-
This post did not contain any content.
lemme yt-dlp this message so I can listen to it in the terminal for less distraction
-
I am fan of reinventing stuff that was frankensteined to kinda work in a modern world..
I don’t like hacky solutions.
Hope systemd is next.
*frankensteind
-
This post did not contain any content.
This again? Insert "wheel was reinvented plenty of times" comment here.
-
I am fan of reinventing stuff that was frankensteined to kinda work in a modern world..
I don’t like hacky solutions.
Hope systemd is next.
Hope systemd is next.
OpenRC, Runit, dinit, s6, ...
-
Not sure how this applies when:
- X11 was the only standard prior to Wayland.
- GNOME is dropping X11 in a short time.
- KDE's telemetry even five months ago showed 80+% of (that portion of) their userbase uses Wayland, and they plan to drop X11 once they have a concrete set of problems worked out.
- Hyprland and Sway run Wayland exclusively.
- Cinnamon, MATE, and Xfce are working on Wayland sessions. Cinnamon's is there but, I think, still experimental.
- Budgie is working to go Wayland-only.
- There's no sign that Wayland will stop improving from a state that's arguably already much better than X11.
- X11's actual maintainers barely want anything to do with it beyond bug fixes, and the only person who wants to "innovate" it via a fork is a bigot and a fucking moron who doesn't know things you learn in CS 101.
- X11's maintainers are majorly involved in developing Wayland and have been since the start. This is their idea.
It seems like it went from "Situation: there is one standard" to "Situation: there are two standards developed by largely the same people with one set to replace the other", and then soon: "Situation: there is one standard and one translation layer kept around for a decade or so for compatibility."
Not every single time someone tries to make things better is this xkcd relevant; this had nothing to do with unifying standards and everything to do with superseding one.
> Pretty much everything uses wayland now
> nVidia drivers don't work on Wayland
> ANGER
And that's why I'm getting AMD when I'll be
modernizingreplacing my setup -
> Pretty much everything uses wayland now
> nVidia drivers don't work on Wayland
> ANGER
And that's why I'm getting AMD when I'll be
modernizingreplacing my setup> nVidia drivers don’t work on Wayland
What?
I'm using Wayland with nvidia-open drivers and I don't have a problem even using proton via Wayland for HDR.
-
Hope systemd is next.
OpenRC, Runit, dinit, s6, ...
The init wars!
(There is a comic somewhere here)
-
> Pretty much everything uses wayland now
> nVidia drivers don't work on Wayland
> ANGER
And that's why I'm getting AMD when I'll be
modernizingreplacing my setupObligatory "it works for me". I only had one issue with one game on Wayland. Some nvidia driver update fixed that a few months ago.
-
> nVidia drivers don’t work on Wayland
What?
I'm using Wayland with nvidia-open drivers and I don't have a problem even using proton via Wayland for HDR.
I'm using the proprietary ones on Bazzite and they don't let me change my refresh rate - fortunately it only went from 75Hz to 60.
When I looked up the issue, the only reason I could find is that the drivers have issues with Wayland.
-
I'm using the proprietary ones on Bazzite and they don't let me change my refresh rate - fortunately it only went from 75Hz to 60.
When I looked up the issue, the only reason I could find is that the drivers have issues with Wayland.
wrote last edited by [email protected]Ah.
I've used a few distros that locked specific patch levels and that's just one of the kinds of issues you deal with. Sometimes that version has a bug and you have to wait for the next major release to get the update.
I'm using a rolling release distro, which comes with a different set of problems. But, I have the latest drivers and Wayland updates and have not encountered any significant issues using high refresh rate, VRR, HDR even while gaming.
It's also possible that Bazzite is using gamescope which does have significant issues with NVIDIA, even still. But the newest versions of Proton support using Wayland directly (instead of XWayland), so it's possible to avoid using gamescope entirely without losing access to display features.
-
This post did not contain any content.
Resisting the urge to reinvent the wheel to run myself over with it
