Curl vs. Wget • Hacker News Board

Re: Curl vs. Wget

#201

Post by daxelrod » Fri, Mar 04, 2016, 4:14 PM UTC

k3n wrote: post #90

daveguy wrote: post #80

Earlier quoted context omitted.

Thanks for the jq tip. I hadn't seen that before. Link if anyone's interested: https://stedolan.github.io/jq/

Underscore CLI looks interesting as well, though I haven't personally had much of a chance to play with it. It does require NodeJS, which might be a deal-breaker for some, but if it's already in your toolchain then it might come in handy. https://github.com/ddopson/underscore-cli

I've written a similar tool underscore-cli and jq called jowl. It's designed to be easier to learn (for JavaScript developers) than underscore-cli or jq. The README includes a comparison.

It's still early in its development, and would benefit from a tutorial and a few more features, but it's getting there.

https://www.npmjs.com/package/jowl

Re: Curl vs. Wget

#202

Post by jkbr » Sat, Mar 05, 2016, 11:26 AM UTC

hobarrera wrote: post #183

geerlingguy wrote: post #13

Also putting this out there—for nicer REST API interaction on the CLI, and a little more user-friendliness, you might also want to add HTTPie[1] to your toolbelt. It's not going to replace curl or wget usage, but it is a nicer interface in certain circumstances. [1] https://github.com/jkbrzt/httpie

I find httpie's lack of manpage quite disturbing though.

https://github.com/jkbrzt/httpie/issues/248

Re: Curl vs. Wget

#203

Post by arm » Sun, Mar 06, 2016, 11:58 AM UTC

troyvit wrote: post #115

xd1936 wrote: post #56

wget has the amazing flag `--page-requisites` though, which downloads all of an html documents' css and images that you might need to display it properly. Lifesaver.

wget has another great flag, -k, which changes references to the css, js, and images to absolute URLs, resulting in a 1 page download that still looks like the original page. It's useful for making dummy pages for clients. I wish curl had this for my OSX friends who need the functionality above. Getting a wget binary onto OSX is a pain but curl is there by default.

Whoa, nice, thanks for the tip! That’s amazingly useful and I seriously wish I had known about it earlier!

For OS X users, you can get wget pretty easily with Homebrew¹. Just install it, then enter the following:

brew install wget --with-gpgme --with-iri --with-pcre

…well, those extra options aren’t strictly needed. Just what I used since I wanted wget compiled with support for those things (GnuPG Made Easy², Internationalized Resource Identifiers³, and Perl Compatible Regular Expressions⁴).

You can see all the compile-time options before installing wget by typing in:

brew info wget

――――――

¹ — http://brew.sh/

² — https://www.gnupg.org/related_software/gpgme/

³ — https://en.wikipedia.org/wiki/Internationalized_resource_ide...

⁴ — https://en.wikipedia.org/wiki/Perl_Compatible_Regular_Expres...

Re: Curl vs. Wget

#204

Post by cyphar » Mon, Mar 07, 2016, 5:09 PM UTC

majewsky wrote: post #157

cyphar wrote: post #125

Earlier quoted context omitted.

Arch Linux has pacman, which is a single program that does all of the things you need from a package manager. OpenSUSE systems have zypper, which also has one command for everything (and has a much more reliable format -- rpm).

How is RPM a more reliable format than dpkg? I've worked with both systems as part of writing a program that generates pacman/dpkg/RPM packages, and I've found dpkg to be the most sane and well-designed of the three, while the RPM format is a horrible and under-documented atrocity.

I meant more reliable than Arch Linux's format. I haven't really worked with dpkg much, so I can't comment.

Re: Curl vs. Wget

#205

Post by Flenser » Thu, Mar 10, 2016, 3:45 PM UTC

DannyBee wrote: post #89

Really interesting. Under curl he has: "Much more developer activity. While this can be debated, I consider three metrics here: mailing list activity, source code commit frequency and release frequency. Anyone following these two projects can see that the curl project has a lot higher pace in all these areas, and it has been so for 10+ years. Compare on openhub" Under wget he has: "GNU. Wget is part of the GNU projec…

"almost all copyrights owned by Daniel." and "389 people own the copyright to curl" aren't mutually exclusive. I think Daniel was saying that most of the code is copyright to him, and you are saying that the rest is copyright to 388 other people.