One of the first tools I install every time I buy a new machine
HTTPie: a CLI, cURL-like tool for humans
11–20 of 53 posts
Re: HTTPie: a CLI, cURL-like tool for humans
#12Earlier quoted context omitted.
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?
I think I understand what you're saying, but all it would be is a change of ownership/packaging. httpie is only an interface to lower level libraries which already exist (requests and therefore urllib3).
Whether it's an interface to requests or to libcurl matters fairly little. It'd be quite a drag if it were to libcurl in fact because syntax highlighting would be a lot harder, for example.
Re: HTTPie: a CLI, cURL-like tool for humans
#13Re: HTTPie: a CLI, cURL-like tool for humans
#14Re: HTTPie: a CLI, cURL-like tool for humans
#15Right, let's take the human denomination away from people that use cURL...
A minor logical point, but no one said cURL was not for humans. More than one thing can be "for humans".
Re: HTTPie: a CLI, cURL-like tool for humans
#16Right, let's take the human denomination away from people that use cURL...
That's not a charitable interpretation of the headline. They are saying that HTTPie is more user friendly.
Re: HTTPie: a CLI, cURL-like tool for humans
#17Earlier quoted context omitted.
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?
By that logic, if Firefox were implemented with libcurl and bundled with cURL, it would no longer need to exist as a separate project.
I'm not sure I understand your point.
Re: HTTPie: a CLI, cURL-like tool for humans
#18Earlier quoted context omitted.
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 legitima…
> 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.
Kind of like titling a project "X: a CLI, Y-like tool for humans"...
Re: HTTPie: a CLI, cURL-like tool for humans
#19There's also a nice auto-complete utility built on top of HTTPie:
Re: HTTPie: a CLI, cURL-like tool for humans
#20Earlier quoted context omitted.
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 legitima…
[deleted]