Re:Hot code reloading with Erlang
by stingraycharles on Friday December 04, 2015 @06:50AM
(#10675782)
On the contrary, the implementation of Erlang's hot code reloading forces state to be separated from the code. If you look at Erlang's gen_server, every call requires you to return a new State object, which is passed to the next function call.
In other words, you can compare the Erlang's virtual machine with a container itself, and everything old is new again!
In other words, you can compare the Erlang's virtual machine with a container itself, and everything old is new again!