VisualWorks Smalltalk VMs had this ability, provided you were a bit careful about how you modified the system. The system would update atomically, and if you were doing things like adding instance variables that safely defaulted values, the system could update in the middle of transactions, then complete them with the new code base. There was the caveat the adding an instance variable to a class meant that every instance of the class basically had to be recopied with the new slot, which could potentially pause the VM for a significant span of time while it performed this operation.
There are embedded RTOS that have similar capabilities. Sometimes, you just want to get very close to zero downtime.
The entire tree concept he is talking about seems like a misplaced faith that you can achieve that kind of separation.
My gut says that in moderate to large sized programs so much state would end up under the root, just out of laziness, time constraints, over-complexity or lack of programmer skill, that you'd have the worst of all worlds.
I just caught the end of the global variables era and have worked on a few programs where the state of things can get modified anywhere.
It is not pretty.
Not pretty is an understatement. It's ugly at best, and rage inducing most the time.
One of my personal policies is to not introduce any new acronyms in the work I do, and especially don't redefine ones that are already familiar in the programming field. Just come up with a proper descriptive name, even if it's slightly longer. Let the acronym follow once the name is already known.
Seeing as how your friend worked for the EPA, maybe I shouldn't be surprised that this phenomenon often seems to surface within organizations whose name is typically given in the form of an acronym...
What, and why would you want to upgrade during a loop?
>Those concepts are replaced by discovery – potentially in an infinite graph of stateful resources
What?
>To achieve large scale, robust, resilient, maintainable, extensible, eternal systems,
So many buzzwords...
Could someone give an example with before/after-pseudocode. I understand neither what the problem is nor the how the proposed solution is expected to solve it.