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
andwget
.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/orwget
to fetch maps from Web services).For some reason, Microsoft's team decided to put aliases for
curl
andwget
in Windows PowerShell – but, as this thread begins, those aliases don't delivercurl
andwget
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
andwget
users."
-- submitted from IRC
(Score: 3, Informative) by Username on Tuesday August 23 2016, @02:08PM
I’m not sure if wget in powershell calls inet or not but i’d like to take this opportunity to gripe about inet anyway, especially how version 11 of inet takes 10x longer to get anything than previous versions. I don’t know if I’m missing some new parameter, or if it’s some kind of energy/resource saving thing. It’s unacceptable to turn a one hour operation into a 10 hour one just by having a single different library. This kinda crap is why people bundle libraries.