3 ms·

> Check out out security tool! Okay. > Install via `curl | sh` (and requires sudo!) Are you fucking serious?

• cookiengineer 3y ago
  A lot of the requirements that come with typical frameworks and their usage are often installed via shell script due to the complexity of installing and configuring them, which I know from my own ebpf stuff is the reason they probably had to ship it with a bash/shell script. I specifically chose golang because it allows me to abstract away that, and I can tell my customers just to download the binary from xyz.url and then execute "sudo binary install" while it does the rest, with zero dependencies. Doing that in say, rust or C++ might be possible but often is not trivial when you take a closer look at what library needs what other linked library. Including the "internet of headers" usually explodes in size of the binary and is very hard to manage, strip out, update and keep up with upstream. I think that is also why I prefer CGo over other FFI-based bindings or the Rust binding ecosystem. Purego is just way easier to use than anything else in practice. But yeah, that's just my two cents. Nobody that uses Rust seems to care about "installation experience" these days. But if you tell your customers to install an SDK first, they likely gonna nope out of your product before they even tried it out.
  • insanitybit 3y ago
    Rust ships static binaries fwiw You can even statically link your libc.