Title

  • Mnglw@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    still frustrating as all hell, these programs just worked on x11

    also Synergy/Barrier/etc dont work yet and would need “non standard” protocols. Pretty critical for me

    I am an enduser and I just expect things to work, but one of the most critical things of my setup wont

      • Mnglw@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        10 months ago

        I will be forced to, but x11 is no longer being developed, so its not very secure to do so

        additionally, Wayland is going to be default on kde, and Im not sure if that means that it’ll be default for me too if I update

        not to mention that with it default on KDE, I’ll be running into more and more bugs that just, will not be fixed, because “use Wayland” will be the new response to bug reports (GNOME actively does this with a critical GTK4/libadwaita bug)

        the point is, Wayland is being rushed and was never ready for default

        • null@slrpnk.net
          link
          fedilink
          arrow-up
          0
          ·
          10 months ago

          x11 is no longer being developed

          Says who?

          additionally, Wayland is going to be default on kde, and Im not sure if that means that it’ll be default for me too if I update

          So when it’s the default, you just pick X11 from the drop-down, like I do for Wayland today.

          not to mention that with it default on KDE, I’ll be running into more and more bugs that just, will not be fixed, because “use Wayland” will be the new response

          Speculation. Gnome devs are notoriously stubborn, I don’t see that being true for KDE.

          the point is, Wayland is being rushed and was never ready for default

          15 years is not a rush, and for most people it’s ready. Making it the default will serve as a push to get developers to make their applications support it.