3 ms·
The edit-compile-run cycle is relatively slow compared to REPL-capable languages or small codebases in compiled languages. As a developer that's really noticeab
by jacques_chester 8y ago
The edit-compile-run cycle is relatively slow compared to REPL-capable languages or small codebases in compiled languages. As a developer that's really noticeable and it's the impression we take with us.
But a warm JVM is a thing of beauty.
Hopefully Graal and Substrate will make this a non-issue in the coming years.
- soulnothing 8y agoJooby supports hot reload https://jooby.org/doc/devtools/ https://jooby.org/doc/devtools/ But It works better under gradle, and that is a whole nother battle.
- lmilcin 8y agoI have worked with Java for over a decade for large companies and I can sympathise. Restarting everything to reproduce the case just to see you forgot something very tiny is painful. That's why my new framework of choice is Clojure (Leiningen, Luminus) on the server and ClojureScript with Reagent and Fighwheel on client side. The app starts moderately quickly but once it starts I have REPLs to both server and client side and I have reasonably reliable reloading of everything when I edit it. Once it starts I can add services on backend side and then immediately write client side ui to consume them, all without even reloading the page. As soon as I save any file on either client or server side it is automatically reloaded without me having to do anything. I can even use same code on client/server side. Have I mentioned it is the same language?
- fulafel 8y agoGraalVM compile times are rather high IIRC.