Curl author asks Microsoft to remove 'curl' and 'wget' aliases from PowerShell

Re:Curl author asks Microsoft to remove 'curl' and 'wget' al... by tobias3 on Friday August 19, 2016 @09:41AM (#12319859)

They could have just bundled cURL with PowerShell/Windows like macOS does. But NIH, I guess?

[ Parent | on HN ]

Re:Curl author asks Microsoft to remove 'curl' and 'wget' al... by UnoriginalGuy on Friday August 19, 2016 @10:19AM (#12320156)

Powershell is an object world, cURL is a string utility. You wouldn't want to bundle it, you want people to use Invoke-WebRequest (current cURL alias).

The alis just needs to be removed. They should replace it with a manpage that suggests cmdlets for popular UNIX commands if those commands aren't found (e.g. if curl returns "not found" it tacks on, "You could try XYZ cmdlet instead").

[ Parent | on HN ]

Re:Curl author asks Microsoft to remove 'curl' and 'wget' al... by jodrellblank on Friday August 19, 2016 @02:02PM (#12321996)

Powershell is an object world, cURL is a string utility. You wouldn't want to bundle it, you want people to use Invoke-WebRequest (current cURL alias).

Specifically, for non PS users reading, Invoke-WebRequest returns n object with the page content parsed and a live DOM to work with, as well as the request headers and the raw data. It's very convenient.

Including curl.exe would not do that.

[ Parent | on HN ]