3 ms·

The situation with curl is different because these are unix utilities you can run on Windows (hence the issue). Now "sudo" is not a very Windows-y name for thi

The situation with curl is different because these are unix utilities you can run on Windows (hence the issue). Now "sudo" is not a very Windows-y name for this utility but it has the advantage of being self-descriptive by those most likely to use it. It's sudo... for Windows. You don't have to explain it further. The command line namespace is flat and there are only so many letter combinations, the idea that an OS shouldn't reuse a command name from a different OS is pretty limiting.

jraph 3y ago
> The situation with curl is different because these are unix utilities you can run on Windows (hence the issue). Good point, the unlikeliness to ever run the real sudo on Windows makes it less an issue. Though doesn't remove it completely. You could for instance imagine a bash script (which you can run on Windows, since you can install Bash there) trying to use sudo if present, or something else, and fail because sudo is present but doesn't have the expected features. In shell land, the name of a command is almost an implicit contract. > The command line namespace is flat and there are only so many letter combinations, the idea that an OS shouldn't reuse a command name from a different OS is pretty limiting. In practice: - Programs are mostly cross platform so many "commands" can work on different OS. Which makes the command line namespace quite shared between OSes - I've not seen many clashes. I can certainly remember of one: the Chromium browser and the Chromium B.S.U game. It was unintentional. The "sudo" one is. You can certainly avoid it.