They did say it was inspired by cargo, which is often installed using rustup as such:
reply curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shI don’t love this approach either (what a security nightmare…) - but it is easy to do for users and developers alike. Having to juggle a bunch of apt-like repositories for different distros is a huge time sink and adds a bunch of build complexity. Brew is annoying with its formulae vs tap vs cask vs cellar - and the associated ruby scripting… And then there’s windows - ugh.
replyI wish there was a dead simple installer TUI that had a common API specification so that you could host your installer spec on your.domain.com/install.json - point this TUI at it and it would understand the fine grained permissions required, handle required binary signature validation, manifest/sbom validation, give the user freedom to customize where/how things were installed, etc.
Given you're about to run a binary, it's no worse than that.
replyIt is definitely worse. At leas a binary is constant, on your system, can be analyzed. Curl|sh can give you different responses than just curling. Far far worse
replyOnly if you download an analyse it. You’re free to download the install script and analyze that too in the same way. The advantage that the script has is it’s human readable unlike the binary you’re about to execute blindly.
replyThis is fitting for something simulating cargo, which is a huge supply chain risk itself.
reply[flagged]
replyIf you'd just left off "to fuck" you'd end up way less downvoted, if it even happened at all.
replyWith fucks, without fucks, in iambic pentameter, anything vaguely critical of Rust will be downvoted. As you can see.
reply[flagged]
replyKnowing the reason something is considered bad does not immediately change that fact that it is considered bad.
replySocial / emotional signals still exist around that word.