SoylentNews

"exec" writes:

Well, that didn't take long: within a week of applause for Microsoft's decision to open-source PowerShell, a comment-war has broken out over curl and wget.

For those not familiar with these commands: they're open source command line tools for fetching Internet content without a browser. Apart from obvious applications like downloading whole sites (for example as backup), they're also under the hood for a lot of other toolsets (an example the author is familiar with – GIS tools use curl and/or wget to fetch maps from Web services).

For some reason, Microsoft's team decided to put aliases for curl and wget in Windows PowerShell – but, as this thread begins, those aliases don't deliver curl and wget functionality.

The pull request says the aliases should be spiked: "They block use of the commonly used command line tools without providing even an attempt to offer the same functionality. They serve no purpose for PowerShell users but cause confusion and problems to existing curl and wget users."

http://www.theregister.co.uk/2016/08/23/your_wget_is_broken_and_should_die_powershellers_tell_microsoft/

-- submitted from IRC

Original Submission