3 ms·

Aren't the Rust binaries significantly larger? Wouldn't that be a problem for embedded system and containers? I'm also sceptical to the whole idea. There are t

Aren't the Rust binaries significantly larger? Wouldn't that be a problem for embedded system and containers? I'm also sceptical to the whole idea. There are tons of more interesting problems to solve than replacing an stable solution with a new one just because you don't like GPL.

yjftsjthsd-h 2y ago
> There are tons of more interesting problems to solve than replacing an stable solution with a new one just because you don't like GPL. I think the argument is usually memory safety rather than licensing.
- daghamm 2y ago
  Is that an strong argument in this particular case? This is after all cp and ls we are talking about. For me personally compatibility would be a much bigger issue
IshKebab 2y ago
It uses a single binary like Busybox to solve that: https://uutils.github.io/coreutils/docs/multicall.html https://uutils.github.io/coreutils/docs/multicall.html I agree it's not what I would spend my time on, but I guess some people found this problem more interesting than us. I don't see a problem with that. Security vulnerabilities in GNU coreutils are rare but they happen. Also this would make building and editing the tools more accessible.
- eru 2y ago
  I remember I had some idea for (GNU) grep, but I couldn't even build the damn thing. It's autotools hell.
  - cies 2y ago
    Another good reason besides mem safety (yay!), license (nay!): build tooling (to improve hackability -- yay!).
  - Y_Y 2y ago
    Your distro should do this for you! Apt-source or pkgbuild will do fine, you don't need Nix or Gentoo to have a ready-to-go script for building your own version of some pre-packaged tool.
    - eru 2y ago
      I was trying to build directly from the sources I got from GNU, because that's where I wanted to contribute back to later.
bpbp-mango 2y ago
it started as a fun way for people to learn rust. it got rather more serious afterwards

yjftsjthsd-h 2y ago

> There are tons of more interesting problems to solve than replacing an stable solution with a new one just because you don't like GPL. I think the argument is usually memory safety rather than licensing.

daghamm 2y ago
Is that an strong argument in this particular case? This is after all cp and ls we are talking about. For me personally compatibility would be a much bigger issue

IshKebab 2y ago

It uses a single binary like Busybox to solve that: https://uutils.github.io/coreutils/docs/multicall.html https://uutils.github.io/coreutils/docs/multicall.html I agree it's not what I would spend my time on, but I guess some people found this problem more interesting than us. I don't see a problem with that. Security vulnerabilities in GNU coreutils are rare but they happen. Also this would make building and editing the tools more accessible.

eru 2y ago
I remember I had some idea for (GNU) grep, but I couldn't even build the damn thing. It's autotools hell.
- cies 2y ago
  Another good reason besides mem safety (yay!), license (nay!): build tooling (to improve hackability -- yay!).
- Y_Y 2y ago
  Your distro should do this for you! Apt-source or pkgbuild will do fine, you don't need Nix or Gentoo to have a ready-to-go script for building your own version of some pre-packaged tool.
  - eru 2y ago
    I was trying to build directly from the sources I got from GNU, because that's where I wanted to contribute back to later.

bpbp-mango 2y ago

it started as a fun way for people to learn rust. it got rather more serious afterwards