Going all-in on a Wayland future
blogs.kde.org
Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

cross-posted from: https://lemmy.world/post/39342270

Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.

  • makingStuffForFun@lemmy.ml
    4·
    3 hours ago

    I use Talon voice. It’s software that let’s me use the pc still, due to write severe RSI.

    However, Wayland doesn’t allow a lot of functionality that tools like this need.

    Therefore, anyone who requires a tool similar to Talon, needs X11.

    KDE is out.

    • Domi@lemmy.secnd.me
      1·
      27 minutes ago

      2027/2032 is still some time away.

      However, accessibility features provided by third-party applications may be worse in some aspects. Please open a bug report if you have any special requirements that we don’t cover yet! This is an active topic we’re very interested in improving.

      Let them know what you need.

    • flying_sheep@lemmy.ml
      3·
      1 hour ago

      Wayland compositors lack the APIs necessary for Talon and Wayland support is not planned.

      Sucks that they just claim that and give up instead of trying to work together with Wayland compositors to make this happen.

      I don’t understand why they would drop you like this.

      • enumerator4829@sh.itjust.worksEnglish
        2·
        42 minutes ago

        Because instead of just using a common well defined API, every developer is supposed to ”work together with Wayland compositors”, of which there are many, none of which are up to feature parity with X. Working together with the (at least) three major compositors is far top much work for most projects, if you can even get them on board.

        Every compositor must reimplement everything previously covered by third party software, or at least define and reimplement APIs to cover that functionality. We have been screaming about this obvious design fuckup since Wayland was first introduced, but nooo, every frame is perfect.

        Take a look at https://arcan-fe.com/ for what a properly architected display server could look like instead of the mess we currently have with Wayland. I’m holding off on moving to Wayland for many reasons, and it wouldn’t surprise me if Arcan becomes mature and fully usable before Wayland. If I get to place a bet on either on Wayland or a few guys in a basement with a proper architecture, I know what I’ll put my money on.