JWM (a window library that I plan to use) shows a fully initialized window in 600-700 ms on M1 mac for me. That’s without Clojure, but with JVM overhead
If your estimation of "time to window" is correct, clojure seems like a very bad choice for this undertaking.
I guess you are not familiar with Clojure, it adds a lot overhead over the overhead of the JVM to startup time.
Re:Thoughts on Clojure UI framework
by capableweb on Friday September 10, 2021 @02:42AM
(#28478454)
Just to add some reference to why it can take a long time to start a REPL (for example):
> As it turns out, Clojure start time is a complicated and multi-dimensional topic. Clojure projects are slow to start not only because of JVM — JVM itself starts in ~50 ms — but because of JVM specifics the classes are loaded slowly. Clojure projects are slow to start not only because of Clojure — Clojure itself starts in ~1 second — but because of Clojure specifics, the namespaces, especially not AOT-compiled one, are loaded slowly. And so on.
http://clojure-goes-fast.com/blog/clojures-slow-start/
A more recent comparison of Clojure, Java and some other Clojure-inspired languages:
https://stuartsierra.com/2019/12/21/clojure-start-time-in-20...
I even have a few git-style CLI tools that bootstrap a JVM on each invocation without using optimized graalvm/native images.