4 ms·

One of the weaknesses of Clojure on the JVM is its ridiculously long startup time. How fast does Frege start up on the JVM?

• voxfrege 11y ago
  It's okay, at least when you have SSD or at least decent RAM. Here is an example: ingo@freguntu:~/Frege/frege$ time java -jar fregec.jar -version 3.23.900 0:00.22 62016k ingo@freguntu:~/Frege/frege$ ls -l fregec.jar -rw------- 1 ingo ingo 33426802 Mär 6 12:32 fregec.jar
  • georgewsinger 11y ago
    22 milliseconds? Unless I'm mistaken that's blazing fast?
    • drewr 11y ago
      I believe that's 220ms. Which isn't too bad. But Clojure can usually match that if you AOT everything. It's still too slow for serious command-line utils, though, so you're back to Haskell.
      • tamana 11y ago
        Or using a long-running system daemon to host the VM
  • mike_hearn 11y ago
    Aren't you checking the Frege compiler, there? The complaint about Clojure is that Clojure apps start slow. Frege compiles to Java and from there to bytecode, so you'd need to compare a hello world in both languages to answer the original question, I think.
    • voxfrege 11y ago
      The compiler is a Frege app.
• ww520 11y ago
  Clojure is slow at startup because of the long list of classes have to be loaded at init I think.
  • agumonkey 11y ago
    It's the core namespace that is huge. Also clojure embeds all metadata etc, taking more time than necessary for a script runtime. Clojure guys discussed having multiple builds, a lean runtime for fast boot, and more featured one for repl usage (even more documentation embedded etc)
• nine_k 11y ago
  On a server, it's a non-issue. On desktop, likely, too. Modern Android does AOT compilation. Hopefully by the time Frege is ready for Android this will not be a problem anymore.