4 ms·

If you are thinking I am a sarcastic detractor, I am not. I whole heartedly believe PowerShell is superior in every way that matters to more common POSIX shells

If you are thinking I am a sarcastic detractor, I am not. I whole heartedly believe PowerShell is superior in every way that matters to more common POSIX shells. I was unaware of the difference between Windows and Linux in this regard as I don't tend to use PowerShell on the few Linux systems I run. However, I maintain that it is still a mistake to alias them in Windows because anyone coming from a POSIX shell background will be misled. > the equivalent cmd binaries were `dir`, `move`, `copy`/`robocopy`, `del`. Nit: only robocopy is a binary in the list. The rest are built in to the command shell.

delta_p_delta_x 4y ago
> sarcastic detractor My sarcasm detector led me into thinking you were a sarcastic detractor (heh). I get your point though; perhaps PowerShell should've stuck with the initialism aliases only (`gci`, `cpi`, `ri`, etc) and people wouldn't have nitpicked on this as though it was some powerful argument against PS. Perhaps there could've been a banner saying `hey, this is Windows, use `gci` instead of `ls` with these xyz options`.