3 ms·
So there's a terminology conflation issue, then: people attacking Wayland proper for issues that are actually about the 'Wayland ecosystem'. I could see that ge
by Fellshard 6y ago
So there's a terminology conflation issue, then: people attacking Wayland proper for issues that are actually about the 'Wayland ecosystem'. I could see that generating increasing problems if there is no observable gameplan for or encouragement to develop those pieces people have come to expect of a full desktop stack.
Mind that I have no formed opinion of Wayland myself, having not used it. Trying to deduce probable causes from hearing people duke it out here and elsewhere.
- DCKing 6y agoI would say that's a fair summary. On Linux, there's X11 based desktops and "post-X11" desktops. "Post-X11" would involve implementations of Wayland and Freedesktop Portals [1], using libinput [2] - and some other things I'm forgetting. All these things don't depend on Wayland and run fine on X11 too (heck you can even run a Wayland compositor in an X11 window), but most of this stuff is pretty new, implementations have lots of QA issues, and application adoption is also not fantastic. On X11 you can just talk to the X11 socket directly for what you want as a workaround, but on post-X11 you have to adopt a new means of doing it. And that hurts. [1]: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html https://flatpak.github.io/xdg-desktop-portal/portal-docs.htm... [2]: https://www.freedesktop.org/wiki/Software/libinput/ https://www.freedesktop.org/wiki/Software/libinput/
- Too 6y agoIt's funny that in the case of systemd both the scenario and hence also the complaints were the complete opposite. Namely that systemd does everything, that in an idealistic world should have been decoupled from the core. (Which was also FUD since the internals actually are decoupled and work alone).