Comment by krisdol | Hacker News Reader

Comment by krisdol | Hacker News Reader

Parent Full thread

JVM is slow as heck to start, but an awesome runtim. In an ideal world I'll never have to restart my application or my repl, but in the real world I do it all the time. It's much faster than node.js/V8 when executing heavy tasks.

One reason I might be interested in running clojurescript on node.js is because most web technologies nowadays are written for node.js/javascript first and ported as an afterthought. GraphQL servers on Clojure/Java, for example, are like 3rd class citizens compared to node.js. Google provides nice wrappers to their APIs as long as you're not using clojure. I end up writing things in-house a lot more often than I would with node where I just npm install the package I want and I get something that is maintained by the official author.

Not it is not, blame Clojure implementation.

The (Clojure) "JVM Slow Startup Time" Myth

http://blog.ndk.io/jvm-slow-startup.html

  ~ time java test

Hello world java test 0.11s user 0.03s system 88% cpu 0.161 total

MacBook Pro (Retina, 15-inch, Late 2013)

I think what's missing in your parent but assumed is, within the context of Clojure, startup is slower than ClojureScript. The Clojure runtime is relatively slow on startup.

Unless you restart your server 400 times a day, how does startup times matter, even remotely?

I think your question is better directed upthread: I'm attempting to clarify possible misunderstandings, not arguing for any particular position. But it's important to keep in mind that people have different needs and desires in different contexts. One off the top of my head is something like AWS Lambda. It's not necessarily the context where Macchiato would play a role, but a server context where one might indeed be starting up processes thousands of times a day.

> JVM is slow as heck to star

Wrong. JVM is fast to start. Clojure is slow to start.

Reply on news.ycombinator.com