plotly.js VS picocli

Plotly is based on D3. Has both open-source version and paid option.

https://plotly.com/javascript/

Plotly as our chart renderer

In this lesson, we will go through the steps of using Plotly.js in React. Plotly.js is an Open Source Graphing Library. At the end of this lesson, you should be able to do a simple plot with Plotly.js.

Well, MathML[1] support is (nearly) everywhere now, and as the docs say:

MathML Core is a subset with increased implementation details based on rules from LaTeX and the Open Font Format. It is tailored for browsers and designed specifically to work well with other web standards including HTML, CSS, DOM, JavaScript.

I don't have a lot of experience working with this stuff (yet) but if you can script your MathML objects with Javascript, you should be able to make whatever interactive "stuff" you want in terms of math notation. Now drawing objects and plots and stuff is a different question.

There's stuff like Plotly[2], D3[3], Sigma[4], etc. that might be useful depending on exactly what effects you're going for.

[1]: https://developer.mozilla.org/en-US/docs/Web/MathML

[2]: https://github.com/plotly/plotly.js

[3]: https://d3js.org/

[4]: https://www.sigmajs.org/

This is the end of the lesson. For more information on Plotly.js, check the documentation Plotly.

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"