• Digit@lemmy.wtf
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    16 hours ago

    Plenty life in X11 yet.

    Xlibre running around.

    Pheonix on the horizon. (Zig!)

    • themoken@startrek.website
      link
      fedilink
      arrow-up
      13
      ·
      16 hours ago

      An anti-DEI fork by a wingnut and a project that isn’t even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.

      … I’m not holding my breath.

      • zurohki@aussie.zone
        link
        fedilink
        English
        arrow-up
        8
        ·
        14 hours ago

        If you deal with the fundamental problems of the protocol itself and also provide backwards compatibility… Congrats, you’ve just reinvented Wayland and XWayland.

        Dealing with X11’s problems while still being X11, when X11 is the problem? Yeah, I wouldn’t hold my breath either.

        • enumerator4829@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          3
          ·
          10 hours ago

          The fundamental architectural issue with Wayland is expecting everyone to implement a compositor for a half baked, changing, protocol instead of implementing a common platform to develop on. Wayland doesn’t really exist, it’s just a few distinct developer teams playing catch-up, pretending to be compatible with each other.

          Implementing the hard part once and allowing someone to write a window manager in 100 lines of C is what X did right. Plenty of other things that are bad with X, but not that.

    • ☂️-@lemmy.ml
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      10 hours ago

      xlibre is xorg with some half baked commits that had to be removed from xorg for breaking too much and a guy who is kind of a nutcase.