• z3rOR0ne@lemmy.ml
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    8 months ago

    Look, the people over at Wayland made a solid protocol, sure. But for all the time and effort they’ve put into getting it to the state it’s in today, it’s going to take a long while for all the apps, DEs, and TWMs to be ready. It took so long for the Linux desktop to get to the state it is on X11, which, for all it’s flaws, seems to be easier to develop for than Wayland.

    Wacom Drivers, Nvidia Drivers, DE-Agnostic screensharing, screenshot, eyedropper tools are all in various states of not working/sort of working/working on wayland. This simply isn’t the case with X11. They all just work. That’s kind of a big win for X11 over Wayland.

    It doesn’t matter how light weight and more secure your protocol is if you can’t use the tools you need to get the jobs you need done, whatever those jobs are. That is literally what computers are for at the end of the day, not to lord our superiority over others because our choice of tools are somehow better.

    Yes Wayland is the future, but to say “Wayland is ready” while also saying “many of the apps for Wayland are not ready” ends up meaning that wayland is NOT ready.

    Until the transition between X and Wayland is seamless (no adjusting environment variables), saying we should all just move to Wayland cuz ”is the future" are engaging in the same FOMO tactics that crytpo and AI bros have been doing for years. Fuck that noise.

    You are not somehow better because you use Wayland. And yeah yeah, shots fired, down votes incoming. Come at me tech daddy.

    • angrymouse@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      8 months ago

      You are absolutely right, I use Wayland on KDE cause two different refresh rate monitores but duude, even on amd you have some hassles. It is ok if you change some env variables, not OK for the average Joe.