• dink@lemmy.world
    link
    fedilink
    arrow-up
    28
    ·
    2 months ago

    If you’re going to point fingers, point at the problem, not something you don’t understand.

    Wayland has problems; it is not the problem. X needs a replacement and I strongly encourage you to research why if you don’t understand why. Wayland is relatively new, and has large shoes to fill.

    It will be many years before it has matured enough to fill your and everyone else’s needs, and by then there will a new replacement for someone else to gripe about on the internet.

    • Eugenia@lemmy.ml
      link
      fedilink
      English
      arrow-up
      9
      arrow-down
      2
      ·
      edit-2
      2 months ago

      Wayland is already old architecture by today’s standards. It was designed in 2007 by the same people who did Xorg. Linux should have copied or ported the 2014 compositor version of Android (which is currently the one still used). The license was good for it, and its technology the most advanced (neither MacOS/iOS or Win comes close). But Linux users have allergy on anything coming from Google and so we ended up with Wayland.

    • nanook@friendica.eskimo.com
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      2 months ago

      @dink A fundamental property of X was that it was a networked protocol, it allowed you to display an application running on one machine, on another. The kernel X-server has in no way been inadequate in terms of performance. So that is what I continue to use. Wayland might someday make Linux a viable game platform helping it replace Windows, and in that sense I applaud it, and perhaps Wayland on Wires will eventually make it a viable network protocol but it’s not there yet.