Stories
Slash Boxes
Comments

SoylentNews is people

posted by chromas on Thursday July 04 2019, @03:41PM   Printer-friendly
from the should've-had-an-X12 dept.

Chris Siebenmann, a UNIX herder at the University of Toronto CS Lab, asserts that the death watch for the X Window System (aka X11) has probably started:

I was recently reading Christian F.K. Schaller's On the Road to Fedora Workstation 31 (via both Fedora Planet and Planet Gnome). In it, Schaller says in one section (about Gnome and their move to fully work on Wayland):

Once we are done with this we expect X.org to go into hard maintenance mode fairly quickly. The reality is that X.org is basically maintained by us and thus once we stop paying attention to it there is unlikely to be any major new releases coming out and there might even be some bitrot setting in over time. We will keep an eye on it as we will want to ensure X.org stays supportable until the end of the RHEL8 lifecycle at a minimum, but let this be a friendly notice for everyone who rely the work we do maintaining the Linux graphics stack, get onto Wayland, that is where the future is.

X11, for all its advantages, also has several incurable design flaws relating to security. However, the major distros have not yet been in any hurry to replace it. Wayland is touted as the next step in graphical interfaces. What are Soylentils thoughts on Wayland or the demise of X11?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Friday July 05 2019, @03:03AM (5 children)

    by Anonymous Coward on Friday July 05 2019, @03:03AM (#863336)

    Somebody else linked this the other day. Sorry, can't remember who. Nineteen years old and still pretty relevant to your desires.
    https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ [joelonsoftware.com]
    I don't think he's correct that it is always a bad idea - some things need to die in a fire1 - but you need some major resources behind you to re-implement from scratch.

    1. <cough>systemD </cough>

  • (Score: 2) by bzipitidoo on Friday July 05 2019, @05:13AM (3 children)

    by bzipitidoo (4388) on Friday July 05 2019, @05:13AM (#863365) Journal

    Interesting read, thanks. Another way I've heard it put is, "don't let the perfect be the enemy of the good".

    And yet, the concept of "bit rot" is basically analogous to the aging that nearly all living organisms suffer. If not throwing away all that experience is so great, why do so many organisms die of old age? The biological way of growing new individuals, essentially from scratch, has a lot of advantages, despite the seeming loss of valuable experience in the aging and death of old individuals, and the heavy costs involved in parenting and education.

    • (Score: 0) by Anonymous Coward on Friday July 05 2019, @11:14AM (1 child)

      by Anonymous Coward on Friday July 05 2019, @11:14AM (#863443)

      How can bits rot in the cloud?
      I mean, I understand bitrot on disk where sectors die.
      The cloud is redundant raid almighty copies forever, right?

      • (Score: 2) by bzipitidoo on Friday July 05 2019, @12:09PM

        by bzipitidoo (4388) on Friday July 05 2019, @12:09PM (#863454) Journal

        I meant bit rot in the context of unmaintained software. Changes are always breaking old software.

    • (Score: 4, Interesting) by deimtee on Friday July 05 2019, @02:46PM

      by deimtee (3272) on Friday July 05 2019, @02:46PM (#863490) Journal

      Because you're looking at the wrong levels. The genetic code is what is passed on from generation to generation and it is certainly never rewritten from scratch.
      You should look at organisms as compiled instances of the program. You start them up, run them until the hardware craps out, then recompile on new hardware.
      Each generation adds a few tweaks, swaps a few modules in and out and, if the compiled instance runs well, it gets the chance to copy its code into the next generation.

      ps. I just realised how double-entendred my original wording was - "Nineteen years old and still pretty relevant to your desires." pffft. I didn't even mean to do that. Sorry.

      --
      If you cough while drinking cheap red wine it really cleans out your sinuses.
  • (Score: 0) by Anonymous Coward on Saturday July 06 2019, @06:29PM

    by Anonymous Coward on Saturday July 06 2019, @06:29PM (#863897)

    If you want something systemd-init like without all the journald and logind stuff tagging along, there are multiple choices already.

    But none of them have the resources backing them like systemd has with Red Hat (and now IBM).