picocli VS mordant

Picocli allows using a compiler annotation processor to generate classes at compile time instead [0].

[0]: https://github.com/remkop/picocli/blob/main/picocli-codegen/...

Picocli is a pretty good one for writing CLI apps

"and there are simply no good command line input parsing libraries for Java."

Looks like author missed the most obvious and popular OSS one: https://picocli.info/

The command line example gave me the "ick". It is usually preferrable to parse the command line arguments into one instance of a custom "command class", rather than into a list of things. Like jcommander, picocli or jbock do.

Complex argument parsing needs to be auto-generated by libraries like picocli. Even if you need something custom, it'd be quicker to write an Annotation processor from scratch than editing that file.

https://github.com/remkop/picocli

"Picocli-based applications can be ahead-of-time compiled to a GraalVM native image, with extremely fast startup time and lower memory requirements, which can be distributed as a single executable file."

https://picocli.info/quick-guide.html

Using picocli to handle your command line options gives you the best chance to automatically generate an ArgumentCompleter script in the future, but won't help you today (other than possibly making your command line handling more standardized & easier).

Picocli

Then we released a JBang! and picocli based cli that would be, on any OS running a jvm runtime :

picocli : "a mighty tiny command line interface"

I'm currently using Picnic and Mordant which are working nicely. I've tried out Kotter and Text-IO, but they either open a Swing terminal or require you to run a `.bat` script or something.

> Many languages have libraries for ANSI color support and pretty printing, but no other language has Rich:

https://github.com/ajalt/mordant