3 ms·
"the painful startup time kind of negates the excitement a newcomer might have towards REPL-oriented development." But you just need to start up once and then
by leephillips 13y ago
"the painful startup time kind of negates the excitement a newcomer might have towards REPL-oriented development."
But you just need to start up once and then work all day in the REPL. Unless you mean that the JVM startup means that Clojure is not a good choice for writing utility scripts and such.
EDIT: As pointed out to me below, and in the excellent talk linked above, it's much more the Clojure bootstrapping time, which almost dwarfs the JVM startup time.
- omaranto 13y agoThe startup time that makes Clojure unsuitable for utility scripts and such is really Clojure's, not the JVM's! JVM start up time is actually quite small these days. See for example, http://nicholaskariniemi.github.io/2014/03/19/solving-clojure-boot-time.html http://nicholaskariniemi.github.io/2014/03/19/solving-clojur...
- stcredzero 13y agoHeh. Back in the day, Smalltalk had a reputation for being too slow to write command-line apps and utility scripts. There were even bits of wonderful tech developed that could produce Smalltalk images as small as 45k! But even more surprising: You could take the default VisualWorks, tell it to skip the herald sound and the splash screen and shut a few other things off, and it would load its 12MB default image faster than Perl 5 could start up with a 768k memory footprint.