No, MS has been “shipping” curl with Windows for ages, it’s just that legacy powershell has an alias for curl to their internal download module that predates the bundling. And they won’t change that because it has backwards compatibility risks.
Upside is, it’s a literal alias. “curl” uses the internal module while “curl.exe” uses the normal app.
Further upside, if you use the up to date version of powershell, that alias is gone as they removed it during the transition.
curl has entered the chat
Invoke-WebRequest has entered the chat
🫠
In Powershell 6 it actually is cURL for what it’s worth
Isn’t that still just an alias for
Invoke-WebRequestthough?At least, I heard again of that being the case not too long ago. Might have also been outdated information, though…
No, MS has been “shipping” curl with Windows for ages, it’s just that legacy powershell has an alias for curl to their internal download module that predates the bundling. And they won’t change that because it has backwards compatibility risks.
Upside is, it’s a literal alias. “curl” uses the internal module while “curl.exe” uses the normal app.
Further upside, if you use the up to date version of powershell, that alias is gone as they removed it during the transition.
Ah, that makes sense. Thanks!