9 ms·
All of that is outweighed by the fact that Wayland does not "just work" in the same way Xorg does. I absolutely despise x11, it's far too long in the tooth and
by smoldesu 4y ago
All of that is outweighed by the fact that Wayland does not "just work" in the same way Xorg does. I absolutely despise x11, it's far too long in the tooth and needs to be replaced by literally anything. MacOS has been using Quartz for the better part of a decade, and on Linux, your choice of window servers is either Tweedle-Dee or Tweedle-Dum. If Wayland's developers hadn't used wlroots as a purgatory for salient concerns about their project, then we might have a good starting spot. If they created a Xorg-agnostic interface for running a Mutter shell on legacy desktops, that would be even better. But we got nothing. They cut real features like AppIndicators straight out of the project for no good reason. They left every other desktop environment out in the cold.
People understand that Wayland isn't a drop-in replacement for Xorg, and that's becoming a problem. People want to run desktops that aren't GNOME or Sway, people want to use hardware that isn't AMD-based, and people want to use the software they've always had just like they did before. Wayland doesn't do that, and after 10 years of antagonizing Linux software development, I think it's safe to say it failed.
- hollerith 4y ago>I think it's safe to say [Wayland] failed In that case I think it is safe to say that all the apps I have been using for over a year have been talking to my window server using a failed protocol. But I really like the experience.