• Mr. Satan@lemmy.zip
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    22 hours ago

    Ok, valid, is sudo (in this case) actively developed? Hom much maintenance does it require?

    All these analogies amount to what exactly? New == better?

    I get the enthusiasm for new shiny thing, especially when the new tool is better. But why do we need something like sudo rewriten? How does it make lives easier?

    There’s a saying: if it ain’t broke… I’m trying to figure how and why it’s broken and all I see just a selling pitch for the language.

    • starelfsc2@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      12 hours ago

      The analogy is “this building is working and tested, but it something DOES break it’s a huge pain to fix it.” whereas in rust it would be relatively painless. I don’t know if that’s worth rewriting it in rust but if the rust fanatics want to do it then eh why not.

      • Mr. Satan@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        11 hours ago

        Well that’s a very valid argument. If cost and impact of an error is very high and a rewrite mitigates that, sure, why not rewrite it. But in this comment thread I had to offer this argument myself, I haven’t really seen it properly communicated.
        It’s always — memory safety this, error handling that… These are good reasons to pick a language for a new project, but, god damn, it’s a stupid reason for a stable program rewrite (let’s say the program is mostly in maintenance mode: no major new features are planned; correct me if that’s not the case for sudo).