4 ms·

I guess the other side of the coin is, right now, what is the killer client app for Wayland? If I have an X11 desktop that works for me, why should I bother la

by hakfoo 3y ago

I guess the other side of the coin is, right now, what is the killer client app for Wayland? If I have an X11 desktop that works for me, why should I bother launching a new compositor plus XWayland, or looking for native replacements for my software? The sales pitches seem to revolve around the architecture being more secure because random window A can't read random window B (and BTW that means your media player's global hotkeys stopped working). It's hard to not see that as a "the killer is already inside your house, so locking yourself in the linen closet is really effective" perspective. I can recall looking at galleries in the late 1990s thinking "I really want to get Linux on my 486 clone because I want those awesome window managers". I don't look at what Wayland has to offer the same way. There are a few compositors lean into the eye-candy mindset (Wayfire comes to mind), but they don't shout out with the boldness of an old Enlightenment release, or even the classic dignity of WindowMaker or FVWM, just some worn-out "let's add transparency and make the windows wobble when you drag them" tropes that were nifty for 10 minutes when we first saw them under X11+Compiz.

jdub 3y ago
There won't be a killer app for Wayland specifically. It's infrastructure. It's also not the place where all the showy (but ultimately annoying) user interface fluff will be found. It's infrastructure. The question is what can it do that X can't, and there are plenty of examples mentioned in this thread (including no tearing, high refresh rates, multiple monitors with different DPI, etc).
- aragilar 3y ago
  But the issue is those things are nice to have, whereas X is baked into existing workflows that either do not work on wayland, or only work on a subset of compositors (due to philosophical disagreements), and many of these workflows have been around for a while, and there is no desire (or funding, or time) to change them.

by hakfoo 3y ago

jdub 3y ago

There won't be a killer app for Wayland specifically. It's infrastructure. It's also not the place where all the showy (but ultimately annoying) user interface fluff will be found. It's infrastructure. The question is what can it do that X can't, and there are plenty of examples mentioned in this thread (including no tearing, high refresh rates, multiple monitors with different DPI, etc).

aragilar 3y ago
But the issue is those things are nice to have, whereas X is baked into existing workflows that either do not work on wayland, or only work on a subset of compositors (due to philosophical disagreements), and many of these workflows have been around for a while, and there is no desire (or funding, or time) to change them.