PowerShell Curl Alias Issue

Supporting information When Microsoft introduced Powershell, it introduced a misfeature where the words "curl" and "wget" were aliased to "Invoke-Webrequest", something that has caused a lot of issues, including: • Bug reports to the "curl" project relating to usage of the Invoke-Webrequest cmdlet • Users having to type "curl.exe" to invoke the real "curl" This issue was raised back in 2016, but at that point, removing that default alias was determined to be too late, because it might break earlier scripts. See this blog article: https://daniel.haxx.se/blog/2016/08/19/removing-the-powershell-curl-alias/ This is a similar case of something similar that happened in the past, and evidence of potential issues in the future if this is not addressed.

A dark-themed screenshot presents supporting information about PowerShell aliasing “curl” and “wget” to “Invoke-WebRequest,” listing bugs and user frustration caused by the behavior. The joke is the dry, overly formal technical explanation of a notorious compatibility issue, shared as a reaction to software design decisions that create future problems. The screenshot presents supporting information about PowerShell aliasing “curl” and “wget” to “Invoke-WebRequest,” listing bugs and user frustration caused by the behavior. The joke is the dry, overly formal technical explanation of a notorious compatibility issue, shared as a reaction to software design decisions that create future problems.

• @gentoomemes / 11523 2024-05-27