Document why this project exists about xh HOT 2 CLOSED

It would be good to have this in the README, yeah.

My reason for using it is its speed. HTTPie unfortunately has a long startup time, enough to be annoying. xh can be 10+ times as fast on requests to localhost, or even 50+ times if you disable coloring (which is weirdly expensive).

Other advantages over HTTPie:

• It releases as a single statically linked binary, so it's easier to install and carry around.
• It supports HTTP/2 (without a plugin).
• It has a builtin translator to curl like https://curl2httpie.online/ (#69).
• --help's output fits on your screen. (help gives longer output, like HTTPie's.)

Downsides:

• It doesn't have all of HTTPie's features.
• You can't disable HTTP/2 (#68), and large downloads over HTTP/2 perform badly (#49). (A solution has been merged in reqwest so we can fix the download speed after its next release.)
• It may never have anything like HTTPie's plugin system.
• General immaturity. HTTPie has seen a lot of real-world usage, that's hard to beat.
• Worse documentation. HTTPie's docs are very impressive, and you can even try out commands right on the webpage using termible. (Maybe we could do that by compiling to WebAssembly?)

Differences:

• Headers are sent and printed in lowercase (because of the libraries used).

I can't think of any (important) deliberate incompatibilities with HTTPie. There are a few edge cases it handles differently, but they should only come up rarely.

from xh.

One more advantage xh has over HTTPie is that it uses rustls instead of the system's installed TLS library.

from xh.