With the 2026.08 ISO release, Artix switched back to Xorg. The switch had been decided soon after the 2026.04 release, due to the unusually high amount of XLibre-related bug reports on our forum and started with our weekly ISO images. This resulted in backlash from XLibre and a veteran Artix developer, Artist, was targeted and harassed, which led to his resignation.

Those XLibre developers must be lovely people…

  • esc@piefed.social
    link
    fedilink
    English
    arrow-up
    38
    ·
    edit-2
    5 hours ago

    Oh wow xlibre was shit from the very beginning who could have predicted this? Super unexpected!

    Reading the linked forum thread is a gift, so many crazy peope at the same place that accuse each other being DEI hires and lefties, but this is a gem:

    You guys have no idea what a mess Xorg’s source code is. I only made very small changes, but I had to spent HOURS on verifying each small thing, because changing only one line of code will cause some entirely unrelated part of the code to completely break in ways that you cannot even imagine.
    You cannot even properly debug a lot of the time because you don’t know which parts of the code use which functions. The code is a giant function pointer soup that is passed around everywhere and nobody knows which parts of the code use which functions as a consequence.

    So exactly the reason why wayland happened.

    • lemmysmash@piefed.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 hours ago

      You guys have no idea what a mess ${THING}'s source code is. I only made very small changes, but I had to spent HOURS on verifying each small thing, because changing only one line of code will cause some entirely unrelated part of the code to completely break in ways that you cannot even imagine.
      You cannot even properly debug a lot of the time because you don’t know which parts of the code use which functions. The code is a giant function pointer soup that is passed around everywhere and nobody knows which parts of the code use which functions as a consequence.

      Here you go. Now you can just do export THING=literally_any_piece_of_software_on_earth_you_want_to_complain_about and just reuse the template xD

    • XLE@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      May I have some context? Too far outside of Linux to recognize who these people are (and usually assume “libre” usually means “good”)

        • curbstickle@anarchist.nexus
          link
          fedilink
          English
          arrow-up
          3
          ·
          3 hours ago

          Ah! Another round of “drama!”.

          And the fun with neovim over the past day. I wonder if they use XLibre or Omarchy lol

        • bring-april-plenty@kbin.earth
          link
          fedilink
          arrow-up
          1
          ·
          3 hours ago

          you had me until I followed the link. the readme when xlibre was forked is a very reasonable, apolitical take and didn’t have me immediately write it off.

          I really don’t understand the wayland issues. I get it didn’t or doesn’t have some features of X but that’s how everything goes.

          • zurohki@aussie.zone
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 hour ago

            Wayland was rough a few years ago and people who tried it then before switching back to X11 think it’s still the same.

            The Wayland devs have been hard at work hammering out all the edge cases and getting Nvidia’s drivers working properly, so a lot of stuff that didn’t work in 2022 or took effort to set up works out of the box now.