• Shareni@programming.dev
    link
    fedilink
    arrow-up
    11
    arrow-down
    4
    ·
    7 months ago

    Imagine using a so called modern protocol that leaves you unable to change a WM in a DE

    Who needs xorg bloat when you can make compositor devs reimplement it instead and bloat their own codebase lol

    • xuniL@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      9
      arrow-down
      2
      ·
      7 months ago

      There isn’t such thing as a WM under Wayland. There are only compositors which make up everything such as the WM, Effects compositor, io etc. To standardize things for smaller compositors things like wlroots exist. Creating a basic compositor using that is around 100 lines of code

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

        Yeah, and that was my point: Wayland turns DEs into inflexible monoliths. You trade modularity, customisability, and stability for better scaling, high-end monitor support, and theoretical security.

        • 0x4E4F@sh.itjust.worksOP
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          edit-2
          7 months ago

          The theoretical security part is what got me “huh 🤨” as well… like “ok, but all of this is planned… or in the works… or it should work… when does the “it does work” part kick in 🤨”.

      • MonkderZweite@feddit.ch
        link
        fedilink
        arrow-up
        3
        ·
        7 months ago

        There are only compositors which make up everything such as the WM, Effects compositor, io etc.

        That’s the thing i don’t like about Wayland.