The biggest thing I can think of is that X11 is more flexible when it comes to specifying custom resolutions; which some people use to output 240p on CRT TVs for emulation. AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

I’ve also noticed that Grsync’s password prompt is broken on Wayland. Thankfully, it has a feature that lets you preview the command it’s about to run, so that you can copy and paste it into a terminal.

Being a KDE user on EndeavourOS, I use Wayland everyday. I switched over a few years ago for Waydroid, but now X11 isn’t even an option for me with the current release of KDE.

  • Aria@lemmygrad.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 day ago

    Wayland can sorta do all three, but they’re effort to set up and sometimes have bugs, whereas it was perfect under X:
    1: Rotate, flip or scale a display.
    2: View a window on a different computer
    2.5: View a window on a different computer that’s already alive.
    3: Overlap two displays.

  • fum@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    Screen saver? At least I haven’t found one yet for Gnome. Or is this a gnome issue?

    • mrbigmouth502@piefed.zipOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      KDE doesn’t have them either, and they’re something I sorely mess. Whenever I emulate or virtualize Windows, sometimes I like to let it go idle and just watch its screensavers.

  • octobob@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    The switch 2 emulator told me to only run it in X11 as wayland still has performance issues. I didn’t really notice much difference running it in xwayland tho

  • aim_at_me@lemmy.nz
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 days ago

    Honestly so many tiny annoyances I used to have with x11 have just gone with Wayland. Multi monitor especially seems so much easier to work with.

    • paris@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      I’m on Wayland and have literally never had any issues with those features. Are these problems you’ve previously had or do you have recent examples where they don’t work as expected?

  • amorpheus@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 days ago

    Run on older video cards.

    My home server has a basic Quadro K420. Since the latest KDE forced it onto Wayland, it’s unusable even for the short remote sessions I need the GUI for. Chrome hangs if I don’t disable HW acceleration, within minutes Firefox leaks memory to the point where the kernel panics, Transmission’s window gets garbled like I’m watching a coded PayTV channel.

    Installed xfce and everything is back to normal. Of course nVidia shares some of the blame here, but it’s clearly working on one windowing system and not on the other.

    • mrbigmouth502@piefed.zipOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day ago

      KWin doesn’t support them, and the KDE devs in their stubbornness see no reason to. I really have a love/hate relationship with this DE.

      • Maki@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        1 day ago

        Same. Unfortunately a few family members decided it was what they wanted for their first foray into linux and I have to try to support it for them.

    • swelter_spark@reddthat.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      Isn’t there a version of xscreensaver that works with Wayland? Besides that, there’s Wayfire’s rotating cube.

    • MangoCat@lemmy.sdf.org
      link
      fedilink
      arrow-up
      0
      ·
      2 days ago

      There’s no timed desktop lock?

      The technical reasons for a screensaver pretty much vanished 10+ years ago, the security aspects are stronger than ever.

      • Maki@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        2 days ago

        Sometimes you just want to have a screen showing you pretty colours on a random rotation. kde’s plasma just goes dark and kicks back to login, and kwin then crashes 9 out of 10 times on resume. Problems I never had with xscreensaver on openbox.

  • Sina@beehaw.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    Forcing vsync on the pointer is my biggest gripe with Wayland right now. (this has a latency cost which is quite perceptible with a gaming mouse, even with 250hz)

    AFAIK, there is currently no real equivalent for xrandr on any Wayland compositor.

    What do you mean? Over half of the wayland WMs can use wlr-randr at least that is working decently well.

  • oopsallnaps@piefed.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    Just wanted to point out that you can create custom resolutions on wayland with kscreenctl (or kscreen-doctor.) I use it to create to enjoy the enlightened 2880x2160.

  • Alavi@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    3 days ago

    Just looking at these comments, and the fact that wayland still isn’t as good as x11 after all these years (10, 15?) And all this budget shows that wayland is architectually wrong and will never be actually good.

    Any software engineer will understand this. If your project is still in basically beta after more than a decade and that much budget, and it’s only selling point is that “but it’s slightly better than the decades old legacy system”, that project has been architectually wrong, and also definitely has awful management, and you call it failed.

    • TehPers@beehaw.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 days ago

      it’s only selling point is that “but it’s slightly better than the decades old legacy system”

      I was sold when I could setup my 1440p@144Hz horizontal monitor and 4k@60Hz vertical monitor in Wayland without any issues. This was after hours trying to get it to work with X11 (and giving up).

      The rest of your comment reads like ragebait, tbh. What, exactly, isn’t as good? What indicates it’s still in beta? What are the flaws? That was the whole point of the post, and “it has problems trust me” is not very helpful.

      • Alavi@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        2 days ago

        read the rest of the comments for that.

        it’s still very unpolished and fragmented from my experience.

    • underscores@lemmy.zip
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      down voted for telling the truth. I use Wayland on my laptop and it works fine, but x11 is honestly still the defacto window system

      I have to use x11 on my desktop (yes Nvidia) and it’s a nightmare. I try it every now and then though

  • 4ffy@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    3 days ago

    My personal bugbear is that there is no compositor-agnostic way to tell what workspace a window is located on. This means that taskbars cannot implement an “only show windows on the current workspace” setting, which frustrates me to no end. (Taskbars like the LXQt and XFCE panels still have the setting, but it does nothing.) There is not even any proposed protocol to support this, and acceptance and implementation would take years even if there were.

    Desktops like KDE probably roll their own custom implementation, but out in Labwc land I’m shit out of luck. (1 2 3 4)

    • ExLisper@lemmy.curiana.net
      link
      fedilink
      arrow-up
      0
      ·
      3 days ago

      Reading those issues… WTF? How many alternative implementation of basic functionalities are there? I think I remember reading back in the day that this will be the issue with Wayland, every DE will have to implement way more than with X. Now I understand what they were talking about.