The fact I even got into this is Joe Armstrong's fault. I was listening to his talk about programming multicores and thought "you know I'm on-board with the actor model across the network, but what's the point of having multiple actors on one machine?" Which lead me down the async rabbithole, which through io_uring ends up reminding me of actors!
yeah. but remrmber that the BEAM is more than just a message queue, its stuff like monitors and links, which are not part of the actor model and confers benefits like why you dont typically have to manually close a file in the beam, or how you can write to a (non-raw) file over the network transparently
(Trick question! A computer has for a long time been a distributed system, we just don't like to worry about that usually.)