2 ms·
Doesn’t wayland force window managers to be integrated into some behemoth bloated monolith? My preferred WM is evilwm. I read the entire source to it in a few
by hedora 5y ago
Doesn’t wayland force window managers to be integrated into some behemoth bloated monolith?
My preferred WM is evilwm. I read the entire source to it in a few hours, and occasionally edit the source when I want to customize it for my odd workflows. I don’t think that’s possible with wayland.
Also, wayland forced a bunch of questionable security policies around screen capture and keyboard handling, and didn’t provide escape hatches required for basic functionality. Is that fixed yet?
I stopped paying attention years ago, to be honest.
- Gigachad 5y agoWhat Wayland changed is that Wayland is not a piece of software like Xorg was. It is simply a specification. Which means you don't have potentially have a 100 line C program as your wm which just relies on xorg to do the heavy lifting. KDE and Gnome have their own wayland implementation but this isn't really a problem. You can still write you minimal WM because their is a project called WLRoots which does the same job as the old x11 package. It lets you trivially interact and be compatible with the wayland spec without having to implement it yourself. Screen capture and keyboard privacy is essential for the future of linux IMO. I don't know the exact state of it but I did not have any issues screen sharing with wayland compatible apps. There were some issues with x11 only apps but I think PipeWire solved that.
- zozbot234 5y ago> Doesn’t wayland force window managers to be integrated into some behemoth bloated monolith? Well, the wayland protocols are very poorly documented compared to X. But most WM's have to support a bunch of obscure X extensions to get a reasonable featureset, that bring in much the same complexity as Wayland.
- kaba0 5y agoWayland is a protocol only. A wayland implementation may choose to incorporate the functionality of a window manager, or can create some way to outsource it to a separate executable. The security policies are not questionable. XServer is beyond fixable. A single rogue extension can screen share everything you do to a remote server, you would not even recognize that.