Curl vs. Wget
daniel.haxx.se
Curl vs. Wget
1–10 of 205 posts
Re: Curl vs. Wget
#2"Wget can be typed in using only the left hand on a qwerty keyboard!"
I love both of these, but wish that curl was just like wget in that the default behavior was to download a file, as opposed to pipe it to stdout. (Yes, aliases can help, I know.)
Re: Curl vs. Wget
#3I instinctively go to `wget` when I need to, uhm, get the file into my computer[1]. `curl -O` is a lot more effort :P
Other than that, curl is always better.
[1] Aliasing `wget` to ~`curl -O` might be a good idea :)
Re: Curl vs. Wget
#4There is no other industry where tools are debated so much as in IT. We literally waste tonns of hours on arguing over minor differences and nuances that really should not matter that much.
Re: Curl vs. Wget
#5There is no other industry where tools are debated so much as in IT. We literally waste tonns of hours on arguing over minor differences and nuances that really should not matter that much.
There's a balancing act between trying to cut a tree with a blunt ax that one never resharpens versus spending all week in an ax store looking at different axes. (Speaking of which I'm doing something like that by looking at hn so I'm not trying to say bad to anyone else because I'd be a hypocrite if I did)
Re: Curl vs. Wget
#6Curl scripts allow open connection to view all new logs in a session.
can wget do similar? I did not know it can or could however from my point of view if it cannot this is like comparing a philips head screwdriver to a powertool with 500pc set.
Re: Curl vs. Wget
#7I instinctively go to `wget` when I need to, uhm, get the file into my computer[1]. `curl -O` is a lot more effort :P Other than that, curl is always better. [1] Aliasing `wget` to ~`curl -O` might be a good idea :)
I use wget for downloads because it follows links by default and resume is just -c. I never figured out how to make curl do the equivalent of -c.
Re: Curl vs. Wget
#8There is no other industry where tools are debated so much as in IT. We literally waste tonns of hours on arguing over minor differences and nuances that really should not matter that much.
There's a balancing act between trying to cut a tree with a blunt ax that one never resharpens versus spending all week in an ax store looking at different axes. (Speaking of which I'm doing something like that by looking at hn so I'm not trying to say bad to anyone else because I'd be a hypocrite if I did)
"Give me six hours to chop down a tree and I will spend the first four sharpening the axe." - commonly attributed to Abraham Lincoln
Re: Curl vs. Wget
#9"Wget can be typed in using only the left hand on a qwerty keyboard!" I love both of these, but wish that curl was just like wget in that the default behavior was to download a file, as opposed to pipe it to stdout. (Yes, aliases can help, I know.)
Streaming to stdout is more Unix-y, allowing you to pipe the response into further processes. For example:
curl http://api.example.com/json | jq '.["someKey"]' # etc., etc.Re: Curl vs. Wget
#10I instinctively go to `wget` when I need to, uhm, get the file into my computer[1]. `curl -O` is a lot more effort :P Other than that, curl is always better. [1] Aliasing `wget` to ~`curl -O` might be a good idea :)
I use wget for downloads because it follows links by default and resume is just -c. I never figured out how to make curl do the equivalent of -c.
I don't think you can:
"[Wget's] ability to recover from a prematurely broken transfer and continue downloading has no counterpart in curl."