Carlos Soriano (@csoriano@mastodon.social)
mastodon.social
One thing I saw in comments about the removal of xorg server is that some might not see how much work is/was to maintain xorg server. I understand is hard to see from outside, but maintaining xorg server with the standards we have in RHEL is not a small beast. Let me share some:
  • Fedora@lemmy.haigner.me
    1·
    1 year ago

    Force people to move to Wayland. Everyone that complains about Wayland breaking their setup knows how to install Xorg anyways. But most Wayland problems are software vendors not giving a shit. Make them give a shit by breaking their shit by default on most setups. 10 years was enough time to make your software work on Wayland. If your software doesn’t work on Wayland by now, then your risk management is shit.

    • Dataprolet@lemmy.dbzer0.comEnglish
      1·
      1 year ago

      It’s not only software vendors but Wayland itself lacks some crucial features. For me it’s auto-type and screen magnification - both are showstoppers for me.

      • d3Xt3r@lemmy.nzM
        1·
        1 year ago

        Autotype is already solved - ydotool, wtype and dotool exists (and possibly others as well).

        Screen magnification is already present in KDE (Meta + +, Meta + - to zoom in/out). There’s also a magnifier tool (KMag). There may be similar functionalities in other DEs.

        My issue is the lack of an overall GUI automation tool, ie, like AutoHotkey. X11 had PyAutoGUI, but there’s no such AIO equivalent for Wayland yet, and the PyAutoGUI devs don’t seem to be interested in Wayland support - it’s neither on their road map, nor have they even answered any Wayland questions on their Github page, which is disappointing. But this isn’t Wayland’s fault, when other tools have shown that automating the GUI is possible, we just need someone to put together a complete package like PyAutoGUI / AHK.