Erlang
Does your app leave little “pid” files around to indicate something is running with some OS process id? Or can your app actually start up and detect that some other process in the system is running? And begin communicating with it?
Can those various processes come and go, and yet the system continues to run, perhaps after healing itself?
That is *service* oriented and that seems to be more about messages and not so much about objects. We should have a “programmer’s holiday” where we all pause our current work and play with Erlang for a week. Not that we should all be using Erlang for everything, but we should all be *influenced* by Erlang for everything.
Maybe that’s not a bad idea at all.