argparse-benchmarks-rs VS httpie

You can check out the argparse-benchmarks-rs though that only gives a high level summary.

So besides the git2 conversation, I'd recommend using an argument parser even if its for something basic like lexopt just for help/version, at least you'd error for unrecognized arguments and can more easily expand it in the future.

Unclear whether it has a solid advantage over other things listed at rust-cli/argparse-benchmarks-rs or whether it's just an "I didn't research what already existed" project.

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.

Not strictly an answer to your question, but https://github.com/rust-cli/argparse-benchmarks-rs provides a good survey of option parsing crates in Rust.

As others have mentioned clap is one of the more popular, featureful CLI parsers though it does come at a compile time and binary size cost. We are working on improving that. See argparse-benchmarks for by-the-numbers comparison for the different parsers (ie only stats and no full feature lists). Clap is used by ripgrep, cargo, and many other tools

Compared to lexopt, which inspired this effort, clap_lex makes some different trade offs for flexibility and ergonomics which allows it to handle every case clap needs. There is room for more ergonomic improvements as the MVP was written for clap's needs. argparse-benchmarks-rs has been updated and clap_lex is roughly in line with lexopt for build-times and binary size.

See https://github.com/rust-cli/argparse-benchmarks-rs/blob/main/examples/bpaf-app/app.rs

You can use this link: https://github.com/rust-cli/argparse-benchmarks-rs

btw there are the argparse benchmarks which can be interesting points of comparison (though I haven't decided what is the criteria for being added to it yet).

tested the end points using httpie and sometime curl

There is also HTTPie which I've mostly been using for its excellent `http` CLI as a modern replacement for curl.

However I recently learned that it also has web and desktop client apps which are pretty great too!

https://httpie.io/

If I now starts the application and trigger the endpoint with httpie :

In some projects I've wanted to use HTTPie to test APIs and jq to work with some JSON data. Nix has been really helpful in managing those dependencies that I can't easily get from npm.

httpie

Their project that I am most familiar with is there CLI https://github.com/httpie/cli

me too! or, you can give httpie [1] a try

[1] https://httpie.io