• KubeRoot@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    14 hours ago

    It is an exaggeration in that Wayland isn’t outright killing x, but a lot of the talk surrounding both is that it’s supposed to.

    I interpreted that killing to refer to niche DEs rather than X, and while that isn’t happening yet, yeah, I imagine a future where software stops supporting X entirely.

    maintaining separate configs for what feels like core features was annoying

    That part specifically sounds like the fault of the specific DE? Wayland might be split into protocols, and some functionality might be handled by the portal, but ultimately it’s the compositor handling how it’s all implemented, and the configuration could well all be in one place.

    • TideElysium@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      12 hours ago

      Yeah, I guess I see the two as linked. I don’t think i3 is going to reimplement itself to stay available, nor would I expect them to

      Also yes I phrased myself very badly there: it’s a decision hyprland has made, where there are separate first party packages for core functionality that need their own configs. I’m sure it’s to allow for your own drop in replacements it just felt clunky to me. I don’t really have an issue with Wayland’s actual composition beyond I get lower input latency on X (which seems to put me in the minority), but they are both substantially lower and nicer to use than windows so I don’t care