On Wed, Apr 17, 2024 at 1:48 PM John Mellor <john.mellor@xxxxxxxxx> wrote: > > With X being a completely unmaintainable mess, all new and bugfix > development stopped about 2 years ago. Most disturbing is that for the > last 2 years there have been essentially no security fixes as a result. I have heard that there have been no security fixes, and also that there have. I understand that there is little to no "development" in the X11 space, but as a mature product it doesn't need development so much as a proper "X12". > Some of the original X developers > started Wayland as X reimagined 45 year later for the 21st century > needs. This was a "good idea". > However, given that absolutely everyone today has compute power > on their desk and everyone has a gpu for things like compositing instead > of what was available back when X was designed, they made some major > architectural decisions that will affect some people, like dropping > remote app windows in favour of remote desktops. 1) I don't claim to be an expert on all the architectural decisions that went into Wayland. 2) Given the limitations of 1, what I have read regarding remote app support seemed to boil down to "we don't want to bother, use VNC/RDP/etc." I *do* understand that there have been so many add-ons bolted onto X11 over the years that it needed a rewrite. I also understand that doing remote apps can be difficult; where do the fonts come from? What are capabilities of the local host vs the remote host? WIth modern bandwidth just sending a graphic (instead of events to create the graphic) seems reasonable. But I don't understand the desire to send a *desktop* rather than a single *app*. I don't understand why there isn't a common element that corresponds to the X server that any "Desktop Environment" can use rather than every DE having to implement their own Compositor My "analysis" - if you want to call it that - is that whereas X11 was "tools not rules", Wayland is being driven by the Corporate environment, and hence is "rules not tools". And I understand the Corporate perspective: if someone can hack host A, they can scrape X events leading to data that lets them invade host B, etc. At the end of the day - for me and many other users - Wayland is *not* a suitable replacement for X11. It is possible that it could evolve into one, although this would seem to require every DE to have its own "extensions" into its own version of a Wayland Compositor, etc. And this to me seems to be heading back into the same kind of mess we have today with X11. I yield the soapbox.... -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
