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.
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.
It was all we had 20 years ago
Excreting waste is a byproduct of many necessary functions, biological and otherwise.
It exists and some poor souls go for a swim in it.