Generally not a big fan of this type of writing especially when it’s so wrong.
I’m an old software dev who grew up with curl but I wouldn’t recommend it to anyone new. It’s extremely dated UX that takes a long time to figure all of the quirks out. You will fail thousand times over and is a http client CLI really worth days of your time learning?
Libcurl itself is brilliant but there are much better front ends for it like hurl or alternatives like httpie - use those instead.
Yes it is worth it, because it is available everywhere, and will still be around in 15 years. Learn it once, use it “forever”, everywhere. It’s the same with learning to use sed, awk, etc. They’ve been around for 50 years and will most likely be for another 50.
Generally not a big fan of this type of writing especially when it’s so wrong.
I’m an old software dev who grew up with curl but I wouldn’t recommend it to anyone new. It’s extremely dated UX that takes a long time to figure all of the quirks out. You will fail thousand times over and is a http client CLI really worth days of your time learning?
Libcurl itself is brilliant but there are much better front ends for it like hurl or alternatives like httpie - use those instead.
Yes it is worth it, because it is available everywhere, and will still be around in 15 years. Learn it once, use it “forever”, everywhere. It’s the same with learning to use sed, awk, etc. They’ve been around for 50 years and will most likely be for another 50.
It’s just a http client CLI not a programming language. It’s not that difficult to switch. In fact I use at least 5 different ones myself.
All the more reason to learn and use curl
Yes after you learn all better clients first, sure.
Which do you consider better?
Hurl looks similar to how intellij integrates their http requests feature.