It was first and became heavily used. The project itself is very old and embedded deeply into the ecosystem. Its more of a “there wasnt anything better”, wayland being built as its successor with a more specific goal
Originally written to render the GUI on another machine across a network to where the program is running a bit like RDP, it got bastardised into displaying GUIs on the same machine the app is running on and never lost the fat
A lot of the problems we have now with XOrg simply didn’t exist when it was first written. It’s an incredibly old protocol and that shows in places where technology and/or common use cases have evolved in directions that expose these previously unknown weaknesses.
No support for variable refresh rate for example isn’t a problem when games don’t even hit 60 fps and the most common use case was spreadsheets.
Wayland still hasn’t merged base color support after 4 years and we’re still relying on either gamescope (which also runs on x11) or KDE/GNOME experimental
No 1:1 touchpad gestures (elementary os not included)
This is the only valid concern on this shit tier comment.
Half of these issues used to be common to Wayland, and the other half have nothing to do with display drivers.
Most of the wayland devs are x11 devs, they aren’t stupid and do have real reasons for using wayland, but these aren’t those.
Nah it’s more like xorg bad because:
It cannot handle multi monitors well
it’s slow as shit
you cannot have desktop animations and do anything graphically intensive
it’s buggy
Xorg screen sharing sucks… It just does. I know I’m gonna get shit on for this, but pipewire screensharing is way better when it works.
No variable refresh rate support
No plans for HDR support
No 1:1 touchpad gestures (elementary os not included)
Wayland is just better, unless you have a very niche hardware setup or are trying to use an older Nvidia GPU with the proprietary driver…
Sometimes i wonder why Xorg is exist if it’s shit at first place
It was first and became heavily used. The project itself is very old and embedded deeply into the ecosystem. Its more of a “there wasnt anything better”, wayland being built as its successor with a more specific goal
Originally written to render the GUI on another machine across a network to where the program is running a bit like RDP, it got bastardised into displaying GUIs on the same machine the app is running on and never lost the fat
A lot of the problems we have now with XOrg simply didn’t exist when it was first written. It’s an incredibly old protocol and that shows in places where technology and/or common use cases have evolved in directions that expose these previously unknown weaknesses.
No support for variable refresh rate for example isn’t a problem when games don’t even hit 60 fps and the most common use case was spreadsheets.
citation needed
citation needed
citation needed (have you seen Compiz bruh)
citation needed
citation needed
Yes it does: https://wiki.archlinux.org/title/Variable_refresh_rate
Wayland still hasn’t merged base color support after 4 years and we’re still relying on either gamescope (which also runs on x11) or KDE/GNOME experimental
This is the only valid concern on this shit tier comment.
Half of these issues used to be common to Wayland, and the other half have nothing to do with display drivers.
Most of the wayland devs are x11 devs, they aren’t stupid and do have real reasons for using wayland, but these aren’t those.