4 ms·
This gist narrowly predates Clojure GraalVM tooling that enables eg Babashka and Clojure usage in cloud FaaS with low cold start latency. And quick startup CLI
by fulafel 3y ago
This gist narrowly predates Clojure GraalVM tooling that enables eg Babashka and Clojure usage in cloud FaaS with low cold start latency. And quick startup CLI tools like clj-kondo (a Clojure linter).
It seems there's some WebAssembly related things cooking GraalVM, currently just support for running wasm binaries but will be be interesting to see if eventually we get support for targeting WebAssembly (if WebAssembly one day gets good GC support).
- kasajian 3y agoThe decision to make Clojure JVM based and so slow to startup has slowed it's adoption to a much more significant level than anyone in the Clojure community is willing to accept.
- chii 3y agois slow startup really such a big issue for the use cases that clojure aims to address? I find most web server applications do not require fast startup times. its only recently with the advent of serverless that it is a potential problem. And for desktop applications, the jvm platform itself is the bigger friction, rather than slow startup times. People just didn't prefer the non-nativeness of the jvm for some reason.
- abc_lisper 3y agoOh, we know the reason. It is because UI looked ugly and the latency was high.
- fulafel 3y agoI think the lowish % of people using GraalVM, Babashka and ClojureScript-on-Node and lack of other supporting evidence make this theory dubious.
- abc_lisper 3y agoAnd yet, the percentage of Java programmers using clojure is less than 1%. Looked at another way, how many applications need the fast startup time, and why can’t they be run in a daemon?