blankverse

What is "unique data"? Does it do de-duplication across users? Are you paying only for unique compressed data?

So, in the worst case, for achieving basic code reloading in other erlang like systems(ex.- cloud haskell), we could let every process in the cluster crash and restart with the new version?

The title is confusing! It should have been "Do messages get lost during code reloading in erlang?"

In a prod env, how do you make sure that different versions of your code coexist peacefully?

How would a "reliable message queue + a script engine" be equivalent to a dynamically hot swappable code reloading? Could you elaborate?

Yes, I could not find any examples. Would be great to find out real world examples of people using erlang's hot code reloading in production.

Could you talk a little bit about what happens to processes which are running different versions of the code? Do you make your code backward compatible so that old processes continue to work with the new process? Or do you just let the old processes crash?