Just taken the curl survey, almost all of which was me saying “no I haven’t used curl for that… curl does that? Really?”
If you’re a developer, you’re using curl whether you know it or not, I bet. But you’re also using it deliberately, I imagine. (I grab files with wget for historical reasons, but any time I want to do an actual http thing I use curl. You might use it for both.) Go tell them what you like; you owe them that at least, I think.
@popey I was all, like, wtf it does SMTP? SFTP? MQTT? Crikey. I always thought of it as “very detailed configurable http fetcher” and clearly what I ought to be thinking is “talks to the network in every possible way”
@popey I need to adjust my thinking. It’s normally “do I need to make an HTTP request? Then curl. (Or GET -UuSse if I want to see the headers, for historical reasons.)” What doing the survey has told me is that I should maybe be thinking “do I need to talk to a server? Then curl.” I had no idea it does all the stuff it does.
@pavled exactly. I once heard a person on the MS Word team say exactly the same thing — everybody uses about 10%, but it’s a different 10% — and curl is… probably more popular than Word, so the same vibe applies :)
popey
in reply to Stuart Langridge • • •Stuart Langridge
in reply to popey • • •daniel:// stenberg://
in reply to Stuart Langridge • • •Stuart Langridge
in reply to daniel:// stenberg:// • • •Pavle
in reply to Stuart Langridge • • •Stuart Langridge
in reply to Pavle • • •daniel:// stenberg://
in reply to Stuart Langridge • • •Stuart Langridge
in reply to daniel:// stenberg:// • • •