“Falsehood flies, and truth comes limping after it, so that when men come to be undeceived, it is too late; the jest is over, and the tale hath had its effect: […] like a physician, who hath found out an infallible medicine, after the patient is dead.” —Jonathan Swift

  • 0 Posts
  • 3 Comments
Joined 1 year ago
Cake day: July 25th, 2024
  • TheTechnician27@lemmy.worldtoProgrammer Humor@programming.dev•Hello, Linux DeveloperEnglish
    1·
    19 days ago

    Not sure how this applies when:

    • X11 was the only standard prior to Wayland.
    • GNOME is dropping X11 in a short time.
    • KDE’s telemetry even five months ago showed 80+% of (that portion of) their userbase uses Wayland, and they plan to drop X11 once they have a concrete set of problems worked out.
    • Hyprland and Sway run Wayland exclusively.
    • Cinnamon, MATE, and Xfce are working on Wayland sessions. Cinnamon’s is there but, I think, still experimental.
    • Budgie is working to go Wayland-only.
    • There’s no sign that Wayland will stop improving from a state that’s arguably already much better than X11.
    • X11’s actual maintainers barely want anything to do with it beyond bug fixes, and the only person who wants to “innovate” it via a fork is a bigot and a fucking moron who doesn’t know things you learn in CS 101.
    • X11’s maintainers are majorly involved in developing Wayland and have been since the start. This is their idea.

    It seems like it went from “Situation: there is one standard” to “Situation: there are two standards developed by largely the same people with one set to replace the other”, and then soon: “Situation: there is one standard and one translation layer kept around for a decade or so for compatibility.”

    Not every single time someone tries to make things better is this xkcd relevant; this had nothing to do with unifying standards and everything to do with superseding one.