ht VS json-tail

Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.

HTTPie is great and was a big improvement for me over cURL.

However, I ended up switching to xh[1] as it's significantly faster and I prefer its output.

https://github.com/ducaale/xh

No, but unless portability is a concern or you're massively familiar with curl, you might want to consider xh. It's much more intuitive.

https://github.com/ducaale/xh

xh

wget on the other hand, automatically converts the ñ to UTF-8 hex and resolves the link perfectly.

I've searched the curl manpage and couldn't find a way to solve this. Please help.

I'm having to use `xh --curl` [1] to "fix" the links before I pass them to curl.

[1] https://github.com/ducaale/xh

Very nice, you should add xh to the User-Agents though.

While not a rewrite - one recent tool for making http requests which i quite enjoy is:

https://github.com/ducaale/xh

It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.

So i frequently end up with curl anyway:)

xh: A HTTPie alternative with better performance.

Not to discourage you from exploring and creating new projects but I had been looking for something similar for server testing and came across the xh rust project, modeled after Httpie

For one, you have a better control on the GUI. Don't get me wrong, I actually ship the tools I build also as little servers (example: https://github.com/egeozcan/json-tail) but there are also disadvantages to this.

I've made a half-baked newline separated JSON tailer for my small use case: https://github.com/egeozcan/json-tail

it's super bare-bones, and the golang side of things could have been much better, but it kind of works.