5 ms·

so no eval at runtime which seems not to be such a big deal; we can develop at repl and then bake images for prod

fnordsensei 8y ago
Some of the Cognitect veterans have pointed out that being able to connect directly to an instance and evaluating code at runtime has been invaluable for debugging issues for their clients.
- setzer22 8y ago
  However, I don't see a use case for GraalVM in long-lived server applications. For that, regular JVM clojure will do just fine. On the other hand, using eval is almost never necessary in small standalone utilities.
  - chrisseaton 8y ago
    > I don't see a use case for GraalVM in long-lived server applications GraalVM also includes a better JIT compiler though, which makes long-lived applications much faster. Twitter use it today to run their Scala code.
    - kjeetgill 8y ago
      From Twitter engineer Chris Thalinger's videos[0] it seems like they're using JDK 9 or 10 and graal via JVMCI. Is there more to GraalVM than just using graal with a particular JDK release? [0]: https://www.youtube.com/watch?v=_7yIUkP5LiQ https://www.youtube.com/watch?v=_7yIUkP5LiQ
      - chrisseaton 8y ago
        > Is there more to GraalVM than just using graal with a particular JDK release? Yeah there's a whole world of different ways you can use Graal. https://medium.com/graalvm/graalvm-ten-things-12d9111f307d https://medium.com/graalvm/graalvm-ten-things-12d9111f307d They're choosing to use the JIT from CE Graal (which they've built themselves), via the released version of JVMCI in a released JDK.
- agumonkey 8y ago
  to the point of pushing networked repl in core or near
- dustingetz 8y ago
  agree but also, ClojureScript didn’t have runtime eval for a long time (because the compiler is bootstrapped on jvm) and that didn’t stop anyone. Even today, runtime eval costs sending all of clojurescript over the wire and no dead-code-elimination; cljs users are quite used to not having runtime eval in prod

Some of the Cognitect veterans have pointed out that being able to connect directly to an instance and evaluating code at runtime has been invaluable for debugging issues for their clients.

setzer22 8y ago
However, I don't see a use case for GraalVM in long-lived server applications. For that, regular JVM clojure will do just fine. On the other hand, using eval is almost never necessary in small standalone utilities.
- chrisseaton 8y ago
  > I don't see a use case for GraalVM in long-lived server applications GraalVM also includes a better JIT compiler though, which makes long-lived applications much faster. Twitter use it today to run their Scala code.
  - kjeetgill 8y ago
    From Twitter engineer Chris Thalinger's videos[0] it seems like they're using JDK 9 or 10 and graal via JVMCI. Is there more to GraalVM than just using graal with a particular JDK release? [0]: https://www.youtube.com/watch?v=_7yIUkP5LiQ https://www.youtube.com/watch?v=_7yIUkP5LiQ
    - chrisseaton 8y ago
      > Is there more to GraalVM than just using graal with a particular JDK release? Yeah there's a whole world of different ways you can use Graal. https://medium.com/graalvm/graalvm-ten-things-12d9111f307d https://medium.com/graalvm/graalvm-ten-things-12d9111f307d They're choosing to use the JIT from CE Graal (which they've built themselves), via the released version of JVMCI in a released JDK.
agumonkey 8y ago
to the point of pushing networked repl in core or near
dustingetz 8y ago
agree but also, ClojureScript didn’t have runtime eval for a long time (because the compiler is bootstrapped on jvm) and that didn’t stop anyone. Even today, runtime eval costs sending all of clojurescript over the wire and no dead-code-elimination; cljs users are quite used to not having runtime eval in prod