I’ve been on Wayland for the past two years exclusively (Nvidia).

I thought it was okay for the most part but then I had to switch to an X session recently. The experience felt about the same. Out of curiosity, I played a couple of games and realized they worked much better. Steam doesn’t go nuts either.

Made me think maybe people aren’t actually adopting it that aggressively despite the constant coverage in the community. And that maybe I should just go back.

  • Atemu@lemmy.ml
    132·
    9 months ago

    I’ve got three hard problems preventing me from using Wayland (sway/wlroots) right now:

    1. No global shortcuts for applications, especially legacy applications; I need teamspeak3 to be able to read my PTT keys in any application. Yes I know that could be used to keylog (the default should be off) but let me make that decision.
    2. Button to pixel latency is significantly worse. I don’t need V-Sync in the terminal or Emacs. Let me use immediate presentation in those applications.
    3. VRR is weird. I’d love if desktop apps were V-sync’d via VRR but the way it currently works is that apps make the display go down to 48Hz (because they don’t refresh) but the refresh rate never goes up when typing; further exacerbating button to pixel delay.
      • Atemu@lemmy.ml
        4·
        9 months ago

        If I can get the portal to just forward every keypress (or a configurable subset) to an xwayland window, that’d work for me. (I am aware of the security implications.)

        • jokeyrhyme@lemmy.mlEnglish
          1·
          9 months ago

          I’m not an expert, but my understanding of the Global Shortcuts portal is that it’s very much designed for the push-to-talk use case where an app is not focused but still receives button events for exactly the keys its interested in and no other keys: I think this would cause problems if an app requested every key (e.g. if the request was approved then no keys would work in every other app)

          It’ll be interesting to see how the remaining compatibility/accessibility issues are tackled, either in portals or in wayland protocols

          • Atemu@lemmy.ml
            1·
            9 months ago

            Yeah and that’s great but my point is that I don’t see an obvious way to use it for that in its current implementation. I’m sure you could build it but it’s simply not built yet.

        • imsodin@infosec.pub
          1·
          9 months ago

          As far as I know xwayland in plasma/kde already does that. However as it’s KDE, it is most likely configurable and might not be enabled by default :P