@wirestyle22 said in wget vs. curl:
@travisdh1 said in wget vs. curl:
@jaredbusch said in wget vs. curl:
@wirestyle22 said in wget vs. curl:
@travisdh1 said in wget vs. curl:
@wirestyle22 said in wget vs. curl:
curl
supports FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, LDAP, LDAPS, FILE, POP3, IMAP, SMTP, RTMP and RTSP.
wget
supports HTTP, HTTPS and FTP.
wget
is part of the GNU project and all copyrights are assigned to FSF.
curl
project is entirely stand-alone and independent with no organization parenting at all
curl offers upload and sending capabilities. .Seems to me we should be using
curl
99% of the time andwget
when we have to deal with a lot of things simultaneously? Am I judging that correctly? Otherwise there does not seem to be a benefit.I tend to use
wget
, just because it's what I'm used to. I knowcurl
can do more, but being able to do more isn't always the simple/quick way to go about things, unless you're doing one of @scottalanmiller's one-liners.Just a thought I had when I was testing some stuff on my vultr instance. You'll likely have both.
Curl is native to RHEL/Fedora based systems. While wget has to be added.
Yep, and it's so automatic to install nano and wget for me that it's almost an afterthought, in addition to any VM templates I have available.
Same. I'd imagine it's the same type of argument as nano vs. vi
If you're not using vi/vim, you're just wrong. No real argument.
Realistically, regardless of preference for wget, you should understand how to use curl. (same with vi)