4 ms·

fyi : The vast majority of these commands are aliased within Powershell with the exception of touch

• nerdponx 8y ago
  I'm not a fan of the aliasing because the actual CLI for these aliased commands can be very different from the originals.
  • danso 8y ago
    I was pleasantly surprised when teaching the CLI to discover that PowerShell (and cmd it seems) has similar conventions to bash when it comes to `|` and `>`. But it annoyed the hell out of me that PowerShell aliases `curl` to something that is most definitely not a drop-in replacement for *nix curl. I ended up having to teach people on Windows how to download the proper curl, and then to refer to it as `curl.exe`.
    • captn3m0 8y ago
      Related: There was a RFC to get the aliases removed, but it ended up being rejected. Blog Post: https://daniel.haxx.se/blog/2016/08/19/removing-the-powershell-curl-alias/ https://daniel.haxx.se/blog/2016/08/19/removing-the-powershe... PR: https://github.com/PowerShell/PowerShell/pull/1901 https://github.com/PowerShell/PowerShell/pull/1901 RFC: https://github.com/PowerShell/PowerShell-RFC/issues/16 https://github.com/PowerShell/PowerShell-RFC/issues/16 Decision: https://github.com/PowerShell/PowerShell-RFC/blob/master/X-Rejected/RFC0007-Weak-Aliases.md#powershell-committee-decision https://github.com/PowerShell/PowerShell-RFC/blob/master/X-R...
    • AnIdiotOnTheNet 8y ago
      Why didn't you teach them how to use Invoke-WebRequest instead?
      • danso 8y ago
        Because the class also involved students who had Macs.
• AnIdiotOnTheNet 8y ago
  As a fan and user of Powershell, I'm going to recommend not using the aliases for the unix commands. For one, they won't act the same. For two, Powershell has a much more consistent and well-named set of commands, which also have their own short alias names by default, and of course you can make your own aliases.