3 ms·
That is the very last of my concerns with Clojure, as I usually just launch the JVM once and then start developing while everything is running. I'll take a slo
by jeremiep 11y ago
That is the very last of my concerns with Clojure, as I usually just launch the JVM once and then start developing while everything is running.
I'll take a slower launch any day if it means less code to write, more rubust programs, more code reuse and everything else Clojure brings to the table :)
- Touche 11y agoSlow launch means you tend to write monolithic applications. You can't write cli tools with Clojure. You can't compose Clojure applications. You have to write a big bulky JVM app. Which definitely has its place, but ClojureScript is expanding Clojure's reach.
- tsmarsh 11y agoI find myself restarting the repl once an hour or so, and running lein 2-3 times an hour (I run lein test before each push and lein install after most rebase/merge). I suspect it sticks out like a saw thumb as its the only bit of Clojure that feels significantly bad. OK, given a choice, I'd probably go for Elm style error messages, then go for faster startup time.