Really surprised at [2] given how robust BEAM is elsewhere. Seems it would be simple for a supervisor to be able to check sizes and kill processes over a certain size.  However, actually thinking about it the hot swapping of code and supervision probably works because all the messages&#x2F;ports&#x2F;ets&#x2F;atoms&#x2F;results can sit there separately while the process can be replaced.<p>Thanks for the info!