| When you open powershell it says something like “Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows” Isn’t it disingenuous to claim it is “up to date” when you know there’s a new version and aren’t using it? > “The alias confuses people that are expecting to run curl when they type "curl" (duh)” Yes, once, until you learn what to do about it. Which is … just like any other software annoyance. One you think people would get over decades ago. > “and also causes headaches for the actual curl developers.” Linux users can’t comprehend that the cURL developer doesn’t own those four letters. > “It has very little compatibility with the actual curl command.” It’s not supposed to have. As I said in another comment the aliases were added to be an on-ramp to PS. Why aren’t you also infuriated that “ls” isn’t compatible with “ls”? Because you use the full command name in scripts? Do that with invoke-webrequest. Because you expect command to behave different in PS? Do that with curl. |
probably they can comprehend that MS has a history of making things slightly incompatible so as to achieve lock-in and eradicate competing systems.
Also if any program has been the standard for doing this kind of thing for a long time it's curl, it's pretty much a dick move that someone can't just send a one liner and expect it to work on your system because that is often how you have to tell someone working in another system "yes it works, just use this curl script" and then they can see wow it must be something with my code that is messed up.