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?

  • atzanteol
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    4
    ·
    9 months ago

    Ugh, I do not miss C…

    Errors and return values are, and should be, different things. Almost every other language figured this out and handles it better than C.

    • teawrecks@sopuli.xyz
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      8 months ago

      It’s more of an ABI thing though, C just doesn’t have error handling.

      And if you do exception handling wrong in most other languages, you hamstring your performance.

      • taladar
        link
        fedilink
        arrow-up
        4
        arrow-down
        1
        ·
        8 months ago

        The unofficial C motto “Make it fast, who gives a shit about correctness”

    • uis@lemm.ee
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      8 months ago

      Errors and return values are, and should be, different things.

      That’s why errno and return value are different things.