Wanting them to work is reasonable, but complaining about the lack of anti-cheat makes no sense. The problem is the insistence on client-side anti-cheat to begin with.

It’s implied, because anything would behave the same.

Not that client-side anti-cheat makes any sense anyway.

File-based navigation is often inefficient anyway (symbolic navigation is much better when you can), but if you do need it, that’s what fuzzy finders are for. Blows any mouse-based navigation out of the water.

The only time a visual structure is useful is when you are actually just interested in learning how things are structured for whatever reason, but for that task, tree works just fine anyway.

https://daniel.haxx.se/docs/curl-vs-httpie.html

Httpie and xh only have a small subset of curl’s functionality, and IMO the claims of more intuitive UX is dubious at best. More magical and limiting is what I would say. Httpie in particular is slow as hell, too.

Daniel has a more thorough comparison of features across different alternatives here: https://curl.se/docs/comparison-table.html

It does not take long to use curl, not sure what you’re talking about. There’s not particularly special about what Postman does.

The same way you test any other API. Not really different. I tend to keep my request bodies in separate files organized in folders to keep things tidy.

Curl. Everything you described is not hard to do via scripts. I use it every day for all of my API testing needs. You’re also not limited to the features Postman provides.

You can easily write a script to make curl requests from a CSV.