Our users are often confused by the output from programs such as zip2john sometimes being very large (multi-gigabyte). Maybe we should identify and enhance these programs to output a message to stderr to explain to users that it's normal for the output to be very large - maybe always or maybe only when the output size is above a threshold (e.g., 1 million bytes?)

Current implementation of join can be improved by performing the operation in a single call to the backend kernel instead of multiple calls.

This is a fairly easy kernel and may be a good issue for someone getting to know CUDA/ArrayFire internals. Ping me if you want additional info.

I often use -v just to see that something is going on, but a progress bar (enabled by default) would serve the same purpose and be more concise.

We can just factor out the code from futhark bench for this.

The TornadoVM repository contains a module with several examples. Include more use cases for acceleration with TornadoVM, such as a graphical version for NBODY, filter for photography, block-chain. etc.

Many builds with natives have support for maven classifiers (used to provide separate jars depending on OS). This reduces download size etc.

Please add this to aparapi-jni.