7 ms·
Yep. And 'wget' is often alias for WebRequest in PowerShell. The amount of footguns I ran into while trying to get a simple Windows Container CI job running, oh
by AHTERIX5000 9mo ago
Yep. And 'wget' is often alias for WebRequest in PowerShell. The amount of footguns I ran into while trying to get a simple Windows Container CI job running, oh man
- ycombinatrix 9mo ago"curl" being aliased to "Invoke-WebRequest" is also a massive dick move
- pixl97 9mo agoyea, curl.exe and curl are two different commands on windows. Fun stuff.
- jodrellblank 9mo agoNot "on Windows". In PowerShell 5. PowerShell core removed the curl alias 9 years ago.
- fourthark 9mo agoBut PowerShell 5.1 is still the one that ships with Windows.
- ycombinatrix 9mo agoI do still find Invoke-WebRequest useful for testing, because it is magically able to reuse TCP connections whereas curl always opens a new connection per request.
- jodrellblank 9mo agoIt's a completely new shell, new commands for everything, no familiar affordances for common tasks, so they add user-configurable, user-removable aliases from DOS/macOS/Linux so that people could have some on-ramp, something to type that would do something. That's not a dick move at all, that's a helpful move. Harassing the creator/team for years because a thing you don't use doesn't work the way you want it to work? That is. They removed it in PowerShell core 9 years ago! 9 years! And you're still fixated on it!
- ycombinatrix 9mo agoIt is still present in powershell on my up to date windows 11 machine today, so it is disingenuous for you to claim the alias was removed 9 years ago. It is 100% still being shipped today. The alias confuses people that are expecting to run curl when they type "curl" (duh) and also causes headaches for the actual curl developers, especially when curl is legitimately installed! Why the hostile tone? Pretty rude of you to claim I'm fixated on the issue for years and harassing the powershell development team with zero evidence.
- jodrellblank 9mo agoWhen you open powershell it says something like “Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows 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.
- ycombinatrix 9mo agoNot gonna respond to my point about you getting irrationally rude and upset over my impersonal complaint?
- jodrellblank 9mo agoPretty sure you edited that in afterwards, but here you come into a thread about Copy-Item, instead start talking about Invoke-WebRequest and when I say "start talking" I mean mic-drop calling the developers dicks with no other content. After you've successfully triggered someone into a flamewar (me), you try to take the high road saying I'm the one being rude? Calling that out as well. > "my impersonal complaint" There's a person behind the move whom you are calling a dick. That's not impersonal. And it is rude. I suspect it's Jeffrey Snover, but possibly Bruce Payette or James Truher. Here I address the wider context in a reply to bryanrasmussen: https://news.ycombinator.com/item?id=46182420 https://news.ycombinator.com/item?id=46182420