The uutils project announced tonight the release of Rust Coreutils 0.3, another step forward for this Rust version alternative to GNU Coreutils that has been attracting a lot of interest lately due to Ubuntu 25.10 now using it by default.

Rust Coreutils 0.3 brings improved GNU test suite compatibility with now passing 532 tests, or nearly an 84% pass rate. There is improved error handling and other updates to better match the behavior of GNU Coreutils… Such as the recently noted date issue breaking Ubuntu 25.10’s unattended upgrades.

  • entwine@programming.dev
    3·
    3 days ago

    A rust rewrite of these tools has a lot of potential commercial value, and I can totally see a cloud provider like AWS putting this into some “hardened cloud AI distro” or whatever. They’ll be able to do exactly what they did to Elastic Search, or do the EEE thing and add bugfixes/features that they don’t contribute back in order to make their offering more competitive, make minor changes to the CLI as a lock-in strategy, etc.

    Not licensing this as GPL will inevitably lead to the erosion of freedoms for everyone.

    • LeFantome@programming.dev
      3·
      3 days ago

      I will take that bet.

      There are already other core utils to choose from. The BSD utils are arguably better than the GNU ones for the use case you mentioned (and permissively licensed obviously). Has anybody “forked” the BSD utils and “taken them proprietary”?

      I mean, people can use the code but that does not take away freedom from anybody (at least not in my view).

      I am quite happy to go on record and disagree with your prediction. Time will tell.

      • entwine@programming.dev
        1·
        3 days ago

        You didn’t get my point. AWS is incentivized to offer the best product they can sell to their customers, regardless of license. If the Rust core utils reach feature parity with GNU core utils, then Rust’s memory safety makes it the superior product (at least on security) and an easy sell to customers.

        That is the point at which the license choice matters for what I said: when it’s widely adopted by AWS customers. If it isn’t GPL, then AWS is free to do what I described, and incentivized to do so.

        Sure, if AWS customers widely adopted the BSD tools for whatever reason, then it’d be the same situation. I just don’t see any particular reason for that to happen.