Strit,
@Strit@lemmy.linuxuserspace.show avatar

The problem, as I see it, is that the author of the original Gist does not really want wayland replacements for what he has, but rather what he has to also work on wayland.

Wayland didn’t break everything. It broke what relied on X11 specific stuff, which turned out to be a lot of things. The vast majority of issues still present with Wayland are edge-cases that will only see the light of day when the people with those edge-cases start using wayland. And as long as distros default to X11, that won’t happen. So that distros, like Fedora, started defaulting to Wayland “early” on (yes I put early in quotes, because it’s only perceived as early) is actually a good thing. Makes the compositor developers aware of edge-cases they can’t catch themselves.

I’vge been using Wayland exclusively for over a year and apart from a couple of small bugs, not even missing functions, I haven’t experienced any issues relating to Wayland directly. But that’s for my use case. YMMV as always.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #