Developers can't seem to agree on what command should get rid of a package

Mentioned on reddit[1], but, specifically for the pacman/yay example, the command handles more than just removing a package. `pacman -Rn`/`pacman -R --nosave` removes 'backup' files (roughly equivalent to `apt purge`) and `pacman -Rs`/`pacman -R --recursive` removes orphaned dependencies (equivalent, I believe, to `apt remove --autoremove`). Yum doesn't have equivalents for these my default and it's not relevant to package managers like npm. (although pip could certainly use the recursive option)

[1]: https://www.reddit.com/r/programming/comments/nlb2c9/develop...

PowerShell uses special NuGet packages. PowerShell uses Uninstall-Module to get rid of an Install(ed)-Module. Remove-Module undoes Import(ing)-Module into memory.

I like the consistency of the terminology.

This is a symptom of the more general problem that CLI interfaces usually have very little attention paid to usability. It's not that developers can't agree on what command should get rid of a package, it's that they can't agree on whether a CLI is an interface meant for humans or programs. So you get completely unintuitive user interfaces that break all the time and never DWIM, and user guides so filled with explanations of all the persnickety behaviours in such a useless format, that you end up needing a separate tool (tldr) to augment them.

The tooling doesn't help. Many CLI flag parsing frameworks don't make it easy to give flags and commands aliases.

You could also view it another way: many small tools that could/should have GUIs don't, because so many developers no longer know how to do a GUI that doesn't involve running a web server.

Rubygems uses 'uninstall' too