Live data from Hacker News

HTTPie: a CLI, cURL-like tool for humans

github.com

1–10 of 53 posts

Re: HTTPie: a CLI, cURL-like tool for humans

#5

Right, let's take the human denomination away from people that use cURL...

This tool pops up every few months, not sure why anyone would use it over curl

If this had been made an interface to libcurl, or added to a separate tool in the curl distribution, most of the novel functionality could have been adopted 3 years ago without the need to support a separate project and HTTP library.

Re: HTTPie: a CLI, cURL-like tool for humans

#6

Right, let's take the human denomination away from people that use cURL...

This tool pops up every few months, not sure why anyone would use it over curl

Because the syntax is easier to remember, it has syntax highlighting for js, html and more and it's super easy to send json, form data, headers etc. It's better and quicker for prototyping APIs for example.

BTW, curl is great too but I hate these kinds of posts. I keep seeing people on HN saying "not sure why anyone would use Y over X" completely disingenuously as if they are expressely not acknowledging the legitimate use cases of Y.

Not sure why anyone would use dropbox over a self-hosted sftp server, right?

Re: HTTPie: a CLI, cURL-like tool for humans

#8

Earlier quoted context omitted.

This tool pops up every few months, not sure why anyone would use it over curl

If this had been made an interface to libcurl, or added to a separate tool in the curl distribution, most of the novel functionality could have been adopted 3 years ago without the need to support a separate project and HTTP library.

What do you mean? libcurl is as much a separate project/library as requests is, and this uses requests.

Re: HTTPie: a CLI, cURL-like tool for humans

#9

Earlier quoted context omitted.

If this had been made an interface to libcurl, or added to a separate tool in the curl distribution, most of the novel functionality could have been adopted 3 years ago without the need to support a separate project and HTTP library.

What do you mean? libcurl is as much a separate project/library as requests is, and this uses requests.

Rephrase: If this was implemented with libcurl and bundled with cURL it would no longer need to exist as a separate project because cURL would develop and support it. Does that make more sense?
Post reply on HN