While we wait to see what comes of the new X.Org Server Git branch plans and a possible X.Org Server 26.1 release, several X.Org libraries saw new point releases this weekend. These seldom-updated libraries saw new releases to ship various build fixes and other minor improvements.

Alan Coopersmith of Oracle’s Solaris team and long-time X.Org release wrangler spent a lot of time this weekend shipping new upstream X.Org library updates

  • FooBarrington@lemmy.world
    32·
    11 hours ago

    Actually that is not too far off from being true.

    No, it absolutely is very far off, unless you find actual studies & user feedback. Lets not do weird mental gymnastics to find logic in pure hyperbole. You gotta give me way more than one 1-week-old bug, and one bug that was quickly caught and fixed. Bugs are going to happen in software that is worked on.

    The reason X was stable for a long time is because many new & nowadays important features (like fractional scaling) weren’t being worked on, the ecosystem was mostly frozen. There’s more churn around Wayland because it’s newer & supports more (and often structurally much better) approaches to solving its problems. Don’t want to get caught in that? Maybe don’t use a distro that is specifically known for shipping new software very quickly.

    • Samueru_sama@programming.devEnglish
      11·
      10 hours ago

      and one bug that was quickly caught and fixed

      The performance regression? It hasn’t been fixed.

      Maybe don’t use a distro that is specifically known for shipping new software very quickly.

      You will run into old wayland bugs lol, like GTK4 apps being totally broken on intel.

      https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/38373

      and often structurally much better

      On wayland even getting apps to draw their own icons is a total disaster, and doesn’t help the constant sabotage from gnome of refusing to fix those issues, and don’t get me started on the csd mess which is another source of nightmares.

      Wayland suffers a lot of internal fragmentation, we didn’t see these kind of issues in the move from pulseaudio to pipewire because there is really only one implemenation of pipewire, guess what would have happened a bunch of DEs decided to make their own implementations of pipewire instead?

      • FooBarrington@lemmy.world
        1·
        1 hour ago

        and one bug that was quickly caught and fixed

        The performance regression? It hasn’t been fixed.

        You know - when you list two points, and I refer to those two points in my response, maybe assume that I’m responding in the same order you listed?