• itslilith
    link
    fedilink
    arrow-up
    8
    ·
    7 hours ago

    But is that desirable? I’d rather break things in favor of something better, and provide a way to make the old thing run, than be stuck with ancient baggage

    Also, while that’s true for software, compatibility for old hardware is horrible under Windows

    • el_psd@sh.itjust.works
      link
      fedilink
      arrow-up
      6
      ·
      3 hours ago

      I’d rather break things in favor of something better, and provide a way to make the old thing run, than be stuck with ancient baggage

      Windows is office software first and foremost, designed to be used by people who neither know nor care what an “operating system” is. Every last one of these people is entirely incapacitated by even the most lovingly-crafted and descriptive error message. If Microsoft ever considered a policy like this, the city of Redmond would be razed to the ground inside twelve hours

    • Delilah (She/Her)
      link
      fedilink
      English
      arrow-up
      2
      ·
      6 hours ago

      Rebuilding the app for the newer version is an objectively better solution, because it allows you to take advantage to new features. 64-bit migrations are a game changer for example. But its an ungodly amount of effort. Every single sodding package has a person responsible for building it for every distro that supports it. Its only because its on the distros to make a given program work on their distro that the system works at all. I agree that I’d rather it be rebuilt to fit into the new system. But that’s a lot of work. Never forget that.