Ten Things You Can Do with GraalVM (2018)

Re:Ten Things You Can Do with GraalVM (2018) by kasajian on Saturday July 15, 2023 @04:18PM (#36740567)

The decision to make Clojure JVM based and so slow to startup has slowed it's adoption to a much more significant level than anyone in the Clojure community is willing to accept.

[ Parent | on HN ]

Re:Ten Things You Can Do with GraalVM (2018) by chii on Sunday July 16, 2023 @01:22AM (#36743948)

is slow startup really such a big issue for the use cases that clojure aims to address?

I find most web server applications do not require fast startup times. its only recently with the advent of serverless that it is a potential problem.

And for desktop applications, the jvm platform itself is the bigger friction, rather than slow startup times. People just didn't prefer the non-nativeness of the jvm for some reason.

[ Parent | on HN ]

Re:Ten Things You Can Do with GraalVM (2018) by abc_lisper on Monday July 17, 2023 @07:17AM (#36756596)

Oh, we know the reason. It is because UI looked ugly and the latency was high.

[ Parent | on HN ]

Re:Ten Things You Can Do with GraalVM (2018) by fulafel on Sunday July 16, 2023 @03:36AM (#36744511)

I think the lowish % of people using GraalVM, Babashka and ClojureScript-on-Node and lack of other supporting evidence make this theory dubious.

[ Parent | on HN ]

Re:Ten Things You Can Do with GraalVM (2018) by abc_lisper on Monday July 17, 2023 @07:13AM (#36756561)

And yet, the percentage of Java programmers using clojure is less than 1%. Looked at another way, how many applications need the fast startup time, and why can’t they be run in a daemon?

[ Parent | on HN ]