Eliminating process boundaries

I know a Buddhist joke, it goes like this: “The Dalai Lama walks into a pizza restaurant. The waitress asks him what he wants, His Holiness answers ‘One with everything'”.

When Gautama Siddhartha became the Buddha, his first realization was that he had always been “one with everything.” This was according to his own accounts, one of his most important realizations, implying he had always been the Buddha, and so had everybody else too. Similar constructs exists in software development. Software developers tends to believe in systems of perfect information. Two examples of such systems of perfect information are chess and Tic-Tac-Toe. However, no such systems exists, even though we tend to believe they do. A perfect example of this is the following screenshot I took this morning, which came about due to that the cleaning lady had cleaned my desk during the weekend, and probably jacked out one of my cables to one of my monitors.

Active Events, or Super Signals as I refer to them today, is simply the realization of that my computer is already “one with everything”, due to that it allows me to create systems, where I no longer care about whether or not my functions are executed in-process or out of process. Hence, I simply treat my in-process functions as if they were out of process invocations, allowing me to polymorphistically change my implementations, as if I had the whole World Wide Web at my disposal. And no, this is not science fiction – It’s at your disposal today. And I’d argue it’s pretty useful too 🙂

Published by servergardens

Create .Net Core CRUD APIs wrapping your SQL database in seconds