Your Package Manager's Installer Doesn't Know Fish Exists

You find a new CLI tool on GitHub. The README looks good. You scroll to "Installation" and see the magic one-liner: curl -sSL https://... | sh. You run it. The script downloads a binary, drops it somewhere sensible, and adds it to your PATH by appending a line to your .bashrc. Except you use fish. And fish doesn't understand export PATH=. So the binary is on your disk, but your shell can't find it. You open the install script, figure out where it put things, and manually write set -gx PATH ~/.local/bin $PATH into your config.fish. You've done this before. You'll do it again. This is a small problem. But it's a revealing one. The kind of developer who installs CLI tools from GitHub release pages, who tries new package managers, who runs fish instead of bash because they actually thought about their shell choice, that's your target user. And your installer just told them you didn't think about them. What Is parm? parm is a binary package manager for GitHub Releases, written in Go by alxr