Re:Clojure 15th Anniversary: A Retrospective
by mjul on Saturday October 22, 2022 @04:22AM
(#33296477)
Exactly. It ties to the excessive startup overhead. If you rename things and change stuff you must run the tests in a fresh JVM to ensure that everything has been evaluated in a consistent state rather ad hoc evaluation in the REPL. This means running from the command line in addition to your REPL or restarting the REPL regularly.
[ Parent
| on HN ]
Re:Clojure 15th Anniversary: A Retrospective
by frou_dh on Saturday October 22, 2022 @04:55AM
(#33296626)
I don't know - the kind of programmer who's always worried about every what-if probably shouldn't choose any dynamic interactive language in the first place. There are plenty of language permutations out there for all sensibilities.
Re:Clojure 15th Anniversary: A Retrospective
by synthc on Saturday October 22, 2022 @10:04AM
(#33298406)
But programmers should be worried about every what-if scenario, regardless of language.
Re:Clojure 15th Anniversary: A Retrospective
by funstuff007 on Saturday October 22, 2022 @06:17PM
(#33302701)
> worried about every what-if
I hear you about this, but during prototyping one cannot be excessively concerned with did I change the global state enough such that it's better to just start a new REPL (and have to worry about the associated costs)? And if you ask this question a lot, long running REPLs are not a good idea for development.
Re:Clojure 15th Anniversary: A Retrospective
by synthc on Sunday October 23, 2022 @03:09AM
(#33305174)
for prototyping a long running repl is fine.
For validation/testing starting with a clean slate takes away a lot of my worries.
Re:Clojure 15th Anniversary: A Retrospective
by CraigJPerry on Saturday October 22, 2022 @07:33AM
(#33297396)
There’s a tool called Clerk which among other things resolves this concern about out of sync definitions https://github.com/nextjournal/clerk