Attention Required! | Cloudflare
www.cyberciti.biz

At first I was sceptical, but after a few thought, I came to the solution that, if uutils can do the same stuff, is/stays actively maintained and more secure/safe (like memory bugs), this is a good change.

What are your thoughts abouth this?

  • Fonzie!@ttrpg.network
    2·
    10 days ago

    Mainly memory safety; split (which is also used for other programs like sort) had a memory heap overflow issue last year to name one. The GNU Coreutils are well tested and very well written, the entire suite of programs has a CVE only once every few years from what I can see, but they do exist and most of those would be solved with a memory and type safe language.

    That said, Rust also handles parallelism and concurrency much better than C ever could, though most of these programs don’t really benefit from that or not much since they already handled this quite well, especially for C programs.

    • 0x0@programming.dev
      11·
      10 days ago

      but they do exist and most of those would be solved with a memory and type safe language.

      Maybe.

      Still, there are other sources of bugs beyond memory management.

      And i’d rather have GPL-ed potentially unsafe C code to… closed-source Rust code.