it is an evolution in several senses. one is a more modern language. this in of itself is not useful, but in this case, rust ecosystem provides a lot of good libraries to use. so instead of depending on glibc or some other library, or hand rolling your own stuff, you can statically compile in good libs. this allows for potentially leaner code.
At some places they are intentionally deviating from gnu variant, for example, uu-cp,mv have a -g graphical flag, which gnu variants did not accept in, because they consider themselves feature complete.
I have pull requests against uutils so I’m by no means anti-Rust or against the project
(i read this part later, and just noow realising you are a better dev then me, and thank you).
But I personally would not replace coreutils with it.
Sure, but is there an actual reason to be switching?
Uutils doesn’t seem to be an evolution of coreutils, but a functional clone. What advantage do we get with that?
Note: I have pull requests against uutils so I’m by no means anti-Rust or against the project. But I personally would not replace coreutils with it.
it is an evolution in several senses. one is a more modern language. this in of itself is not useful, but in this case, rust ecosystem provides a lot of good libraries to use. so instead of depending on glibc or some other library, or hand rolling your own stuff, you can statically compile in good libs. this allows for potentially leaner code.
At some places they are intentionally deviating from gnu variant, for example, uu-cp,mv have a -g graphical flag, which gnu variants did not accept in, because they consider themselves feature complete.
(i read this part later, and just noow realising you are a better dev then me, and thank you).
feel free to do as you like.