Originally posted by avis
View Post
Absolutely not true that X servers can be used interchangeably. Anyone who ever played with WiredX and http://nano-x.org/ and many other not x.org X11 servers based found out very quickly that X11 servers cannot be used interchangeably. Interchangeability with X11 server was only happening if the X11 at first was a fork of Xfree86 then X.org as in being based off the reference version of X11 server. Also as you move into these not X.org X11 servers you start finding no graphical driver or very limited graphical driver support support..
Do note that WiredX and nano-x both don't support X11 compositors at all.
Originally posted by avis
View Post
X11 features reach X11 server implementations at different times and there's no guarantee they will even reach yours. If you're not a X11 reference implementation user, your X11 experience could be woefully incomplete.
That line is the reality. Yes Xfree86 was the reference X11 implementation for a time then was replaced by X.org X11 implementation. Yes the different forks off x.org server do have the habit of feature lagging you find this with Xquartz on Macos and Xenocara done by Openbsd by the way.
Basically avis you have way oversold X11. The reality that 99% of Linux distributions used x.org X11 server means most people are not aware of the X11 server problems. I am very aware of the X11 server problems because for a particular use case in the past I had to use tinycore Linux that had what was called microwindows that became nano-x very quickly I had X11 compatibility issues.. Then I had to use a sun workstation and run into X11 server issues again due to quirks in the sun x11 server implementation. I could go on with 40+ pages of every time I had some non x.org/xfree86 X11 server and the different in X11 implementation proceeded to kick me in the teeth.
Now all your counter points avis apply to X11 protocol.
A horrible amount of work required to implement X11 features
Yes this one of the reason why anything not x.org X11 server today or Xfree86 in the past mostly horrible.
A horrible amount of duplication of work
Yes this one of the reason is why anything not x.org X11 server today or Xfree86 in the past mostly horrible.
Minor X11 compositors being unable to implement X11 features due to financial constraints/lack of developers
Notice I just swapped out Wayland for X11 here. Yes this is also true statement minor X11 compositors like the one in xfce is known to be feature lacking in their completeness of the X11 composite protocol compared to Gnome and KDE and this was true before Wayland existed and still true now of course. Of course this X11 compositor problem effects uses of x.org X11 server.
Users of X11 getting radically different experience depending on what X11 server they are using
Again take out Wayland put in X11 get another true statement.
Multiple DEs/WMs struggling to support it
With security updates and other things Multiple DEs/WMs were having this problem before Wayland.
Avis you need to stop presuming X11 was in a very good position when Wayland started. The true fact of the matter X11 in 2008 when Wayland started as a ecosystem was not really in a good place.
Avis you say others don't care about those issues. The reality those issues have been around for a long time. Problem here is the issues you said I first saw in 1996 but applying to X11. Due to these problems being really old means we have never worked out how to solve them.
X11 solutions fairly most worked as long as you only used the X11 reference implementation. Now the wayland case we don't have most parties basing their work on the reference implementation Weston.
Gnome and KDE not basing off Weston is they already had a prexisting item being the X11 compositors they had was 90%+ there to being a complete Wayland compositor. Yes Gnome and KDE could be suffering from sunk cost fallacy leading to failure to cooperate.
Comment