• lambalicious@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    5 days ago

    That has always been my main criticism about wayland: it’s actually vaporware.

    It’s just a spec (and not even a complete one) that says “now, you go do our work and implement all this”. So everyone has to go and do their own thing, which is the usual big corpo strategy to kill small corpo and/or FOSS. So I wonder why don’t people see it. Pulseaudio, wayland, systemd, all came in at about the same time as the “microsoftism” infection in Linux development.

    From what I recall, for the first 5-or-so years there was not even a reference implementation (and I don’t know if that is still the case, but do would expect it is).

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 days ago

      I don’t see how Wayland could be “antifoss.” It is literally controlled by the major desktops. For smaller projects there are libraries that do the heavy lifting.

      The major benefit is that the performance us much better since you don’t have a bloated display server that has decades worth of bad code.

    • lime!@feddit.nu
      link
      fedilink
      English
      arrow-up
      3
      ·
      5 days ago

      i think weston is the reference implementation, but i don’t know if it’s usable

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 days ago

        It is “usable”

        Not a great experience but it does work. Honestly I don’t know why it exists at this point. It is holding back Wayland in a lot of cases and they are sluggish to implement anything.