Half-a-Hundred and counting
Posts: 58
Location: Lafayette,Louisiana,United States
|
I suspect the Primary code is the kernel for the next version of the Matrix. I would conjecture that a program that big is largely compressed by several algorithms that are implemented in several passes.
I would further speculate that this code is stored in the One's DNA. The brain is too volatile and unstable. But DNA uses a base 4 representation, which is jump in storage density of an entire order of magnitude from binary. Given that the vast majority of our gene sets are not believed (by contempory experts in the Genome project) to be active, an enormous amount of data can be stored in each chromosome, without changing the life form phisiologically one iota. On top of that, every non-somatic cell on the human body that has a nucleus has its own seperate copy!
As early as the 1990's genetic engineers had successfully implanted segments of non-protient synthesizing DNA code into plants and fruit-flies which contained data. Coincidentally, one of the first was the universal Venus storaged as 7 by 5 bitmap, which in the language of Linear Algebra is a 7x5 Matrix. Enough digression.
Upon arrival at the mainframe, I envision the provides are small cheek cell sample to the machines which would parse the encoded DNA, uncompress portions of it, then bootstrap the kernel of the new Matrix while incorporating patches specified by the Architect.
The kernel/primary code probably contains a several modules to run the interactive life simulation. Some of the modules might be:
* A physics engine to govern the universe
* An interface template between the plugged human's consiousness and the physics engine.
* A socialogical guidance agent, which would follow a script provided by the Architect which is likely to contain a large number of nested conditional blocks intented to keep history and society on track.
* Security daemon, which would dispatch the familiar Agents to handle glitches and deal with Zion.
* Physical resource manager, which keeps track of the status of the battery farms, and provides information to the socialogical guidance agent, for optimal management of the subjugated population size, age, growth... etc.
* And of course, the standard process and thread control, filesystem and account maintainance modules like the O.S.'s we use.
I would imagine that different modules would be written in different language types:
*the physics engine would likely be written in a runtime optimized, low level procedural language because it would be so active with simple things.
*the society and physical resource managers would have more time to work, thus high level functional languages akin to Scheme or ML might be used.
*the interface templates would have to build themselves, and type polymorphism would be a plus. An object oriented framework with inheritance would not be a good choice.
*The code for events, temporary creations and situations might be governed by scripting languages which reliably handle dynamic memory allocation.
I would guess that of the high level subsystems would make extensive use of distributed network processing, while the lower level (closer to the plugged in denizens) applications would run loop based "main" functions. Whether or not stack based memory allocation would still be around... I don't know.
One thing I can tell you with confidence is: the Architect would not be foolish enough to use Microsoft software or Intel hardware. For the first Matrix the Architect and Smith referenced, the sublime paradise or perfection, would must have been running something based on Mac OS.
As a software engineer, that's my first shot from the hip hypothesis.
|
