3 ms·
A window manager is just an X11-ism. It's nothing more in that parlance than a Gnome plugin. There are "Wayland display server toolkits" out there, so you can
by gf000 1y ago
A window manager is just an X11-ism. It's nothing more in that parlance than a Gnome plugin.
There are "Wayland display server toolkits" out there, so you can just build whatever you want without reimplementing a wheel. But an additional layer allowing for these plugins that X has is just added complexity that not every diplay server would want - e.g. a custom display server for a thermostat.
- arboles 1y agoEmphasis on the plural in "toolkits", X has one standard interface running on people's computers that window managers target. X environments end up having common behavior regardless of window manager, and for application developers having to target each Wayland display server with its own subset of protocols has to be less appealing. That is what that comment was getting at. Application developers don't want to log your keyboard and aren't oblivious to security. The lack of a standard Wayland display server is a real grievance.
- gf000 1y agoWhere is that common behavior, is that GNOME's one, KDE' one, or the million tiny window managers' ones? Would you swear that no "application" developer would want to log my keyboard if we include the transitive dependencies of every single nodejs/python/etc package that I use for regular-ass development? Because we have seen how trustworthy supply-chains are. But sure, you can definitely drive a car without a seatbelt on, it's just not a good idea.
- michaelmrose 1y agoX and Wayland from the perspective of desktop Linux is for computers and what would be good for thermostats is irrelevant. It makes more sense to have an entirely different thing for embedded
- gf000 1y agoWhat about a car entertainment system? A kiosk that is basically a full touch-based desktop, but only displaying a single app? Where is the line?