ProwlerGr
These are good points. But whether xorg or xlibre, will supporting things like GTK2 apps from 20 years ago still be a chore, unmaintained, or at some point, simply be impossible to integrate without a whole lotta’ pain?
I’m cool with that, as long as I’m not the one who has to recompile and do workarounds every release. Let someone else maintain the workarounds, and hopefully they don’t get burned out.
Much of what I see about Wayland with my recent experience with vanilladpup/wayland/labwc is that many of the negative gripes are either stale, or have to do with those trying to run Gnome or KDE desktops with all the bling with some sort of twinkly widget not working like it used to in 1998. Then don’t do that. 🙂 Labwc is the window-manager way for me. And no systemd either.
Sadly, in today’s world, it is sometimes hard to tell who has actual experience, or who are doing fluffy reactionary/grifter “content” just to get a $reward with click-throughs over hot-button topics.
My stance is rather more practical than political, it’s not about getting into an x11 vs wayland debate.
Wayland is the future (or might not be – lets not stick to that), but x11 is still widely used & will continue to be used for at least the immediate future.
We currently have 2 forks of x11:
– xorg maintained by an organisation (or corporation if you like), that has no interest whatsoever to keep maintaining it
– xlibre maintained by a group of volunteers, that aim to modernize it & introduce new features.
By no means would it be wise to jump in & switch to xlibre immediately, as it is unknown for the time being how efficient the team managing the project maybe to addressing bugs/holes etc.
But we would want to know how it currently plays with our distro (in a development build), & potentially participate in filing bugs/raising issues & monitoring how the xlibre project is overall run, before we are forced to drop the (abandoned) xorg.