I don't know who Wayland is - eviltoast

If anyone wants to give an ELI5 or a link to a video that ELI5 I’d be incredibly thankful

I swear that all the stuff I find is like super in depth technical stuff that just loses me in no time flat

  • Shareni@programming.dev
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    7 months ago

    But it’s been an uphill battle because XOrg is the final boss of legacy codebases.

    Also because Wayland forces every compositor to be an unmodifiable monolith instead of following the UNIX philosophy. For example I’m currently running i3 inside of Xfce because the de, wm, compositor, and every other part are doing their own thing and can be replaced. With Wayland I’d need to fork the compositor and spend a ridiculous amount of time on something that’s trivial in xorg.

    And let’s not forget the garbage pile of tools that got abandoned a week after release because Wayland introduces breaking changes on a regular basis. You want unified shortcuts across multiple compositors like with sxhkd? Tough luck, the only tool was abandoned after the first version and doesn’t work anymore. On the other side you’ve got 15 rofi alternatives you need to dig through to find out which ones are still maintained and might work on your device.

    On top of that Nvidia GPUs have so many issues, and while that’s not solvable by Wayland, it’s still a major issue that still hasn’t been fixed after 15 years, but might maybe soon™.

    Finally, the security improvements have gave me nothing but headaches whenever I tried using Wayland. No matter the distro or compositor, screen sharing and recording never worked for me. Give permissions, share whole screen or just window, it’s either black or the program is not showing I’m trying to share ate all.

    You can’t blame it all on xorg when Wayland is still simply far worse for a large part of the community.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      The Wayland protocol board can never agree on anything. It takes them years to decide to consider adding something.

      Also Wayland is just a protocol at the end of the day so implementation is up to the software developers. I also think that the Unix philosophy holds back software that could be good. You shouldn’t prioritize it over good battery life and low overhead.

      • Shareni@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        7 months ago

        I also think that the Unix philosophy holds back software that could be good.

        IMO the UNIX philosophy is the reason why Linux survived. Imagine if every distro had a single DE, or you had issues with pulseaudio and couldn’t replace it with pipewire.

        You shouldn’t prioritize it over good battery life and low overhead.

        And why would separating functionality into different tools cause you to have a worse battery life? You don’t get to have tlp on other OS because it’s all integrated