The curl-wget Venn diagram
daniel.haxx.se
The curl-wget Venn diagram
1–10 of 159 posts
Re: The curl-wget Venn diagram
#2don't forget the weekly security fix on the right side ;)
Re: The curl-wget Venn diagram
#3What are happy eyeballs in the curl circle ?
Re: The curl-wget Venn diagram
#4warc support is smth wget specific, worth mentioning
Re: The curl-wget Venn diagram
#5I guess the most common usage is the overlap between the two. That's why I'd love to see a Venn diagram of where (OS and docker images) each is installed by default!
Re: The curl-wget Venn diagram
#6What are happy eyeballs in the curl circle ?
A fast(er) & standards compatible way of doing ipv6+ipv4 connections.
Re: The curl-wget Venn diagram
#7What are happy eyeballs in the curl circle ?
[deleted]
Re: The curl-wget Venn diagram
#8Mandatory mention for the comparison made by Daniel Stenberg
Re: The curl-wget Venn diagram
#9For me the killer feature of wget is that by default it downloads a file with a name derived from the url.
You do:
wget url://to/file.htm
Using curl, you would have to do
curl url://to/file.htm > file.htm
Re: The curl-wget Venn diagram
#10For me the killer feature of wget is that by default it downloads a file with a name derived from the url. You do: wget url://to/file.htm and a file named "file.htm" appears in your cwd. Using curl, you would have to do curl url://to/file.htm > file.htm or some other, less ergonomical, incantation.