>> Its' interprocess communication is TCP based in general case > No, it is not. Only between machines is that true. It is true for communication between two

>> Its' interprocess communication is TCP based in general case > No, it is not. Only between machines is that true. It is true for communication between two VMs on same machine, isn't it? The general case includes same-VM processes, different VM processes and also different VMs on different machines. > Why are you rolling with "speaking a whole lot of BS based on ignorance" today? TCP is unreliable: https://networkengineering.stackexchange.com/questions/55581/acknowledgment-by-tcp-does-not-guarantee-that-the-data-has-been-delivered https://networkengineering.stackexchange.com/questions/55581... That was acknowledged by Erlang's developers before 2012. I remember that ICFP 2012 presentation about Cloud Haskell mentioned that "Erlang 2.0" apparently acknowledged TCP unreliability and tried to work around.