News for hackers. Stuff that matters.

A comment on Hard-won lessons: Five years with Node.js. Parent comment

Re:Hard-won lessons: Five years with Node.js by ars on Thursday April 20, 2017 @12:57AM (#14154075)
> And with Hotswap, you don't even need to redeploy anything.

Except when you have to restart the JVM because you added a class or a whole bunch of other things that it can't hotswap in the new code.

[ Parent | on HN ]
Re:Hard-won lessons: Five years with Node.js by petersellers on Thursday April 20, 2017 @02:42AM (#14154465)
It's true that the hotswap support built in to the JVM is somewhat limited, but there are tools that are more comprehensive and can hotswap new classes, methods, method signature changes, etc. (JRebel and spring-loaded are the ones that come to mind).
[ Parent | on HN ]
Re:Hard-won lessons: Five years with Node.js by hota_mazi on Thursday April 20, 2017 @01:39AM (#14154237)
Still better than any dynamically typed language (I mean any) where you always have to redeploy everything since none of these language support incremental compilation, let alone incremental reloading.
[ Parent | on HN ]
Re:Hard-won lessons: Five years with Node.js by ben-schaaf on Thursday April 20, 2017 @08:06AM (#14155890)
If I'm using a truly compiled language (eg. C++, D), which have incremental compilation, I still have to redeploy everything since 'everything' is a single executable.

If I'm using an interpreted language I only have to deploy the changed source files. Git can do that for you.

[ Parent | on HN ]