3 ms·
Author of the tool here. I can definitely see why you might think that, but I don't think it's fair to bring my presumed lack of understanding of the command l
by TomNomNom 9y ago
Author of the tool here.
I can definitely see why you might think that, but I don't think it's fair to bring my presumed lack of understanding of the command line up as a reason; especially when some of the documentation[0] is a bit of a pipe party.
I've addressed this a little in another comment already[1], but the truth is that the HTTP client functionality only really exists for the sake of a few users that I heard from directly. curl being a default on Windows now[2] may be enough that this feature can be removed. Perhaps the feature should never have existed, but now that it does it's difficult to justify removing it - you never know whose workflow you might break[3].
[0] - https://github.com/tomnomnom/gron/blob/master/ADVANCED.mkd https://github.com/tomnomnom/gron/blob/master/ADVANCED.mkd
[1] - https://news.ycombinator.com/item?id=16733361 https://news.ycombinator.com/item?id=16733361
[2] - https://blogs.technet.microsoft.com/virtualization/2017/12/19/tar-and-curl-come-to-windows/ https://blogs.technet.microsoft.com/virtualization/2017/12/1...
[3] - https://xkcd.com/1172/ https://xkcd.com/1172/
- cup-of-tea 9y agoFair enough. Might be worth changing the docs to use curl and adding that the built in simple HTTP client is a convenience that exists for limited platforms.