On Tue, 10 Jun 2025, Fungal-net wrote:
On Tuesday, 250610, Olivier Galibert <galib...@pobox.com> wrote:
The problems are the reasons why Wayland is inferior, e.g. the integration of
the window manager into the server (making customization so much more
difficult) and
In the past while discussing functionality with core devs of a wl wm their
refusal to tackle an alternating behavior of some usually X very core choice in
wm, was misunderstood. But what you state here explains perfectly well why a
wm designer will not go to war with wlroot (example) choices to alter behavior.
the balkanization that results from it
Hey, watch it!
It is hard to digest why so many people here and at this level will mention "desktop"
when what they are talking about is the layer below them, the wm. It brings memories of the famous
reaction by Poettering "what do you have against disabled people" back to the foreground.
My main negativity source with wlr-stuff is that I can't as easily shift from user to user to user
within one session and run the same or other applications as different user. To just run the
application containerized as if it is a different session prohibits communication of (clip cut and
paste functionality). Say you have your work split as projects and each project has its own user,
so "sudo -u proj34 abiword" and "sudo -u proj25 mercury" can't share their
clipboard, test or binary. There are ways to cheat this and have a common access saved buffer but
it is too much of a hack and hastle to get all this generically working.
So no matter how much I like labwc it will not replace my X wm choices.
On X you would just do "xhost +" and do what you need to do.
best
Vladimir Dergachev
If my coding skills were anywhere near enough to rewrite vtwm I would, but you
can't teach an old dog new code. Next life maybe.
