• turdas@suppo.fi
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    8 days ago

    Yeah. “Feature parity or get out”, like dude we’re long past feature parity.

    Wayland supports so much more stuff than X11 does, and what does X11 have that Wayland doesn’t? X forwarding? Just use a modern remote desktop solution, all X forwarding was doing in “modern” times (read: the 21st century) was streaming pixels anyway, just less efficiently than modern remote desktop.

    • JojoWakaki@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 days ago

      I switched to Wayland. I think I have almost everything working except keepassxc’s global hotkey and autotype. Also certain apps like ardour, I have to manually break components off from the main window and move to different monitor to get the “multi monitor” functions going. This I know they have been trying for 2 years now, anyday now.

    • redjard@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      5
      ·
      8 days ago

      I still use X forwarding.
      It works just fine using xWayland, and X forwarding has always been so janky there is no chance to notice any difference caused from using xWayland instead of native.

      It will surely take many years and well established wayland native remote tunneling before anyone thinks of ditching xWayland.

    • First_Thunder@lemmy.zip
      link
      fedilink
      arrow-up
      2
      ·
      7 days ago

      Multi window apps are still broken, and the wayland protocol guys have been dragging it for more than two years

    • bobo@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      7 days ago

      Yeah. “Feature parity or get out”, like dude we’re long past feature parity.

      Ok, replace the xfce/KDE wm with something like i3 and then keybind all of the commands that aren’t wm specific through a global hotkey daemon like sxhkd.