Conversation
Notices
-
Embed this notice
@newt @mjdxp @wolf480pl @nytpu x has unfixable issues when it comes to process isolation. some of the early pros to wayland is actually being able to stop every program from becoming a keylogger.
problem is .. idk. i don't honestly know wwhy the wayland devs are all morons. is the problem of splat textures together that insurmountable or is it truly the biggest brain trust who ever lived working on it?
-
Embed this notice
@divVerent @mjdxp @newt @nytpu @wolf480pl I don't see why the compositor can't turn around and outsource the job to a subprocess. That's how X did it.
-
Embed this notice
@icedquinn @newt @mjdxp @nytpu @wolf480pl They cannot agree on simple things and bikeshed on everything forever.
Which is why screen locking is still unsolved on Wayland, with multiple competing half implementations for specific DEs and decades old bugs with discussions.
For the time being, using Linux means instead of relying on Wayland works - see physlock.
-
Embed this notice
@divVerent @mjdxp @newt @nytpu @wolf480pl I thought client side decorations had something to do with the compositor trying to stay out of some crosscutting concerns
-
Embed this notice
@icedquinn @mjdxp @newt @nytpu @wolf480pl It _can_, but it _doesn't_. Basically, on X11 it was outsourced by default (but X servers with builtin window managers exist).
And that is why it is currently in practice harder to have custom window management on Wayland. Wayland was MEANT to bring forth GNOME world domination, alternate compositors were seen as a bad thing to happen (see also: client side decorations, which could only work well in a single-DE environment).
But indeed - someone definitely could make a "W server" that outsources window management and decoration to a subprocess with a clearly defined protocol. No such protocol has been defined yet though, so there we are. wlroots, being a library and not a protocol, comes closest.