When software devs expect you to pipe a script straight from the internet into Bash...
zalgotext @ zalgotext @sh.itjust.works Posts 0Comments 1,220Joined 2 yr. ago
zalgotext @ zalgotext @sh.itjust.works
Posts
0
Comments
1,220
Joined
2 yr. ago
Doing something distro-specific in an install script for a single binary seems a bit overcomplicated to me, and definitely not something I want to blindly pipe into my shell.
The bun install script in this post determines what platform you're on, defines a bunch of logging convenience functions, downloads the latest bun release zip file from GitHub, extracts and manually places the binary in the right spot, then determines what shell you're using and installs autocompletion scripts.
Like, c'mon. That's a shitload of unnecessary stuff to ask the user to blindly pipe into their shell, all of which could be avoided by putting a couple sentences into a readme. Bare minimum, that script should just be checked into their git repo and documented in their Readme/user docs, but they shouldn't encourage anyone to pipe it into their shell.