I’m curious how software can be created and evolve over time. I’m afraid that at some point, we’ll realize there are issues with the software we’re using that can only be remedied by massive changes or a complete rewrite.

Are there any instances of this happening? Where something is designed with a flaw that doesn’t get realized until much later, necessitating scrapping the whole thing and starting from scratch?

  • @hperrin
    link
    -17 months ago

    Wayland, Pipewire, systemd, btrfs/zfs, just to name a few.

    • @[email protected]
      link
      fedilink
      107 months ago

      Wayland is THE replacement to broken, hack-driven, insecure and unmaintainable Xorg.

      Pipewire is THE replacement to the messy and problematic audio stack on Linux to replace Pulseaudio, Alsa etc.

      SystemD is THE replacement to SysVinit (and is an entire suite of software)

        • @[email protected]
          link
          fedilink
          1
          edit-2
          7 months ago

          The only thing I personally dislike about systemd is the “waiting for service to stop 5mins/1h30mins” stuff during shutdowns and reboots. I know I can limit them to 10s or something but how about just making systemd force-stop these services like, say, runit.

          When I’m using my bemenu script to shutdown and feel like a hackerman, don’t take that way from me by being an annoyance, systemd!!!

          Edit: Yes, I’m considering switching to Void, how could you tell?

      • @hperrin
        link
        27 months ago

        Yes, I know. I was answering the question of if there were instances of this happening.