We’ll also need a bit of Elisp for the UI, but that should be trivial. It’d be really great if we had something like squiggly-clojure for kondo, that’s using middleware instead of just evaluating code, so it would return data that’s optimized for the Elisp clients. That can expand the usefulness of kondo to more than linting - e.g. you can directly expose the data needing for find-usages, bake project integration, etc.

Depends on how large your classpath is. Clj-kondo lints some projects in CI: clojure itself, clojurescript itself + some libs, this takes about 10 seconds

Hum.. does IntelliJ and co achieve better speed by being long lived process? As I understand, kondo would do a full lint all the time. But I think IntelliJ for example keeps a full AST of Java at all times and as things are changed, it partially update that AST and only perform analysis related to the changes.

yes, it's the difference between a server that can accumulate state and a binary which is invoked once and lives very shortly.

but if clj-kondo is invoked as a library in a cider middleware you could achieve the same effect probably

Thanks for the info!!

Great info!