bagder

Yes it is indeed by the author of curl! (me ;-)

curl has a --libcurl option which you can add to a curl command line, and then it'll generate a libcurl-using C code template for that same operation...

It all depends on how you count and what a "user" is of course, but this little list helps to give a picture: http://curl.haxx.se/docs/companies.html

I believe they originally come from the libwww-perl project? According to wikipedia it was first released with perl 4.0036, which was in Februrary 1993, but I can't find out if it included GET and HEAD etc already then...

Those were the early days of HTTP, so no, people didn't really get a lot of HTTP "manually" like that. We used other existing tools to get gopher and ftp though.

When I started my work on httpget in 1996, I didn't know about wget and I didn't become aware of it until several years later....

As the author of the document - thanks!

Sorry, but that doesn't make a lot of sense. Pipelining is far from a replacement for HTTP/2 as the document explains a bit. Besides, Safari already supports SPDY because of this.

This doesn't drive the standards process in any particular direction, this is just a broken implementation that doesn't adhere to the current standard draft!