Killing X11 | Hacker News Reader

Killing X11

flak.tedunangst.com

48 pointsgoranmoomin12 comments

Wake me up when wayland just works for basic things I need and use daily, and I don't have to hear some diatribe about why what I do daily is wrong.

(What I do may be "wrong" in some cosmic technological sense, but it's still "the only thing supported by the software vendor" and also "isn't actually broken" in the sense of "works just fine". Unlike wayland, which "doesn't work just fine")

When Wayland has its regularly scheduled "break basic functionality" day of the month, distributions are still to this day telling their users to use Xorg as a workaround until it's fixed. If we want Wayland adoption we eventually have to get our shit together, it has been 16 years of this.

Wayland was a misguided design to begin with, but fine we are stuck with it now. Now we need to get this thing into a stable state and stop people from breaking it every five minutes.

I'm on a pure wayland system, everything been fine for the last two years

Yes, its all a big conspiracy against X11, lets all slander these selfish open source developers that don't sacrifice enough of their time and dare to make technical choices you don't agree with. How about you step up and maintain the X11 backend for "QTK" yourself.

why is BGR chosen over RGB in wayland?

They aren't. This is fanfic

Their point is the project that wants Wayland will randomly make changes like this on their Wayland code in such a way that breaks on X11. They say QTK as a reference to Qt or GTK

GNOME wants Wayland.

Meanwhile (just last week) GTK was broken on Wayland on some older Intel GPUs because of the Vulkan drivers. X11 was spared because the X11 backend still uses OpenGL.

Exciting stuff.

They also broke XWayland via a Mutter change that clearly wasn't tested at all given how quickly the bug reports started pouring in.

https://gitlab.gnome.org/GNOME/mutter/-/issues/4133

So, they don't want you to use X11 AND they don't want to support XWayland properly, either.

None of this will get solved until some programmer does something similar to what the Pipewire guy did and rips the whole system down. In this case, probably starting from the assumption of "Vulkan is the base" and building up from there.

So, a GPU driver broke and that’s Wayland’s fault?

No, but this time it was only Wayland users who were affected, right?

"My applications are empty boxes but only on Wayland."

From what was said in the comment it seems like anything vulkan would have had issues, not just Wayland

worked for systemd

Reply on news.ycombinator.com