| ▲ | jborean93 6 days ago | |
> *nix fanboys were totes fine with wget and ls being an aliases in PowerShell for years but when they found out what PS is coming to Linux they made a biggest stink The curl and wget aliases don’t exist on the PowerShell 7 version which is the cross platform one. Only the old powershell.exe builtin to Windows has these aliases and it’s worse today because curl.exe is builtin and the curl alias takes priority when you run just curl. | ||
| ▲ | justsomehnguy 6 days ago | parent [-] | |
Thanks, I'm with PS since v1.0. > Only the old powershell.exe builtin to Windows It's "Windows PowerShell" which would be forever v5.1 and "PowerShell" is v7+. (we don't talk about "PowerShell Core") > builtin and the curl alias takes priority when you run just curl Yes, but again if somebody didn't bother to read the docs, read the output (it's very evident when you have some PS error vs. everything else - and people STILL don't bother to try to understand) and start bitching on the forums... see my previous comment. And by the way: it was established quite early what the use of an aliases in the written code should be frowned upon, exactly for the reason what the aliases aren't stable and could be local. Aliases are the quick way when you are slapping something interactively in the CLI. So wget/curl were added for the benefit of those *nix fanboys who needed something better than cmd.exe on Windows so they could start using PS faster and later adopt to a proper ways but instead of reading the docs they only rose the stink. | ||