This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-15
Channels
- # announcements (9)
- # babashka (1)
- # beginners (1)
- # calva (7)
- # cider (13)
- # clj-kondo (2)
- # cljsrn (1)
- # clojure (40)
- # clojure-europe (2)
- # clojure-spec (9)
- # clojure-uk (1)
- # cursive (4)
- # datomic (2)
- # etaoin (1)
- # fulcro (4)
- # honeysql (3)
- # lsp (43)
- # malli (7)
- # music (1)
- # nbb (6)
- # off-topic (5)
- # polylith (8)
- # protojure (1)
- # re-frame (6)
- # react (17)
- # reagent (63)
- # releases (1)
- # shadow-cljs (8)
- # testing (8)
- # tools-deps (1)
- # vim (8)
I used / hacked on nailgun some 9y ago it was a pleasant experience, not sure if something has changed though these days I'm not much bothered by startup time. One can learn to tackle the problems that make restarting a JVM perceivedly necessary in the first place. Then your repl session can last weeks/months, as Sean C. shares over here from time to time :) Some random examples: run tests from the repl, learn to avoid defprotocol pitfalls, learn to avoid dangling resources, add abundant, commonly-used libs to the classpath (which doesn't affect startup time!) in advance
Starting up a REPL will consume more power than leaving it open, I believe - it makes your CPUs work full power to precompile things, prepare the runtime, etc...
To be 100% certain you'll have to measure, but if you're working with ClojureScript, you probably will have a REPL open all the time, right? If so, the cost of keeping it open, instead of closing everytime and starting again, will be lower
To be completely honest, I'm not even sure why do you think that keeping the REPL open "consumes more energy". I mean, keeping it open will not do anything...