One of the thing proper to Erlang's hot code loading is that it uses a vm-centralized code server that handles and garbage collects the different versions of co

One of the thing proper to Erlang's hot code loading is that it uses a vm-centralized code server that handles and garbage collects the different versions of code. This server can in turn notify subscribers about code changes; the OTP framework uses this to propagate code upgrades in its behaviours (gen_fsm, gen_event [and all the handlers], gen_server) with a callback function that lets the programmer define what changes to the data structures and state currently in running code have to be applied. Does node.js have anything similar to that? Or is there anything of the kind planned? I don't really know the in and outs of node.js, but from the blog post, it seems like there's no way to update current state and the only real upgrades will be done on new calls. Is this because node.js just doesn't have the same objectives in mind?