I love curl so much. I just learned that you can 'copy to curl command' from the chrome inspector's network panel by right clicking on any request!!<p>I want to make a library that reads the curl command (and maybe request syntax?) and outputs a function that will do that command.
It's slightly weird to me that I am older than Curl and Wget. They always seemed like Unix Monoliths to me; I had just assumed they had always existed.
Curl is great, but I also recently came across HTTPie (<a href="https://github.com/jakubroztocil/httpie" rel="nofollow">https://github.com/jakubroztocil/httpie</a>) which has some nice features for playing around with HTTP APIs (JSON formatting, syntax highlighting, etc)
Daniel Stenberg, the maintainer, was also on the packet pusher podcast recently, talking about HTTP/2 - <a href="http://packetpushers.net/show-224-http2-its-the-biggest-network-thing-happening-on-the-internet-today-repost/" rel="nofollow">http://packetpushers.net/show-224-http2-its-the-biggest-netw...</a>
I was wgetting all my http requests until about 2 years ago. Curl's undeniable coolness won me over after 15 years. Now I practically live in curl when I'm setting up webservices, and libcurl for PHP does something on nearly every page request I have.<p>For PHP people, curl_multi_exec is the new event loop.
curl is just awesome, thanks so much to the author and all maintainers over the years! It's still my go to application for testing and debugging HTTP requests.
Curl is pretty great to use, but be warned it has old smelly code and is probably full of security issues. I wouldn't use it for anything too critical.