picocli VS Quarkus

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"

Meanwhile, if you're building something smaller than Netflix, I'm writing a book just for that (https://opinionatedlaunch.com/).

It's about mobile apps, but I talk about backend at great length, especially since my background is Java. The book is called "opinionated" because I cover Quarkus (https://quarkus.io/), monolith, Fly.io, and no K8s.

Quarkus is a Java based framework tailored for GraalVM and HotSpot, which results in an amazingly fast boot time while having an incredibly low memory footprint. It offers near instant scale up and high density memory utilization which can be very useful for container orchestration platforms like Kubernetes or Serverless runtimes like AWS Lambda.

Other useful articles related to Quarkus extension development can be found under the Writing Extensions guide category on the Quarkus.io website.

Quarkus is one of Java frameworks for microservices development and cloud-native deployment. It is developed as container-first stack and working with GraalVM and HotSpot virtual machines (VM).

If you GraalVM Native Image or one of the frameworks based on it then bootstrap cost disappears:

https://quarkus.io

We are open to practice using any open-source project, however, we want to set a sharp focus on projects maintained by the Red Hat, and our own projects in the Caravana Cloud organization on github. If there is no reason to do differently, we'll build using technologies such as OpenShift, Quarkus, Ansible and related projects.

The Quarkus you are talking about is this one? https://quarkus.io/