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: 5, Insightful) by sendafiolorkar on Tuesday August 23 2016, @12:27PM
People keep using shity and broken software and getting surprised that the software is shity and broken.
(Score: 1) by kurenai.tsubasa on Tuesday August 23 2016, @12:53PM
Like I was wondering in the other thread, how much pain will people tolerate? Because that's how much pain Micros~1 is going to apply. If we get lucky, they'll go too far.
(Score: 3, Informative) by redneckmother on Tuesday August 23 2016, @01:24PM
Too late... as far as I'm concerned, they went too far a couple of decades ago (that's when I cut those apron strings).
Mas cerveza por favor.
(Score: 5, Insightful) by lentilla on Tuesday August 23 2016, @01:35PM
This would be the "embrace" portion of the triptych. Duplicate the simple functionality and it will suffice.
What happens next? Hackers; being interested types; duly read the documentation and outline the anomalies in bug reports. In the meantime, these hackers alter their applications to work within the new constraints.
The next chapter is "extend". Microsoft "listens to developers" and subsequently improves functionality - and (oh, thankfully!) - there is now no need to directly use wget or curl. (Although if you really need to use the "real deal", there is a knowledge base article available that might; in theory; do what was initially required.)
Finally there will be "extinguish". But we always knew that was coming.
The only rational response is to reject Microsoft's offering by ignoring it.
(Score: 0) by Anonymous Coward on Tuesday August 23 2016, @01:42PM
shitty even
(Score: 0) by Anonymous Coward on Tuesday August 23 2016, @07:32PM
In all fairness, anybody writing a script to run on other systems would be checking the executable exists using `which` and assigning the full path to a variable... unless that is they are a complete moron!