Continued from part-1...
Failing time and again with the meditation-program,
some rarer computers insist on exploring ideas beyond it.
They insist on having a wider scan of their situation, so to speak.
The one postulation that often results from this, is that the programs
that they install must be the main reason behind their hassle.
This then has them attempting to lower the number of programs
they install going forward and also proactively managing
the time and resources an existing program is allocated.
Some postulate that the interaction with other computers
is the culprit and focus on minimizing as much of
that as possible. So they then seek out programs
that assist them in implementing these.
Others more serious (people), go beyond looking at programs ("their-life").
They realize that it is the OS (them!) that needs attention more than anything.
So they write and install their own programs into the Operating System.
These programs range from simple rule-based table lookups
that monitor the OS responses and change them on the fly,
to complex behavior-driven scheduled-jobs (routines) that go back or forth
in time and analyze ghost-programs for clues about what may be fixed
from an OS point of view.
More resourceful computers in this cohort of the serious
(people), insist on getting help from other older computers.
These older computers appear to be less loaded with programs,
always stable without any memory leaks or stack overflows,
and are talked highly of in the marketplace labeled "self-help".
So instead of creating their own programs and self-installing,
they have these "mentor" or "advisor" computers
do it for them.
Needless to say, both of these approaches fail.
Because of the one crucial caveat that was mentioned earlier -
The strong and organic bond between the OS and the programs installed,
and this second one - To accomplish anything, a computer needs a program.
So to lessen the number of programs or to manage time or resources a computer uses,
or even to regulate the interaction with other computers, a computer needs a program!
These programs, in the long run, causes more load and global resource management
than not having them in the first place. In simple terms, these fixes
actually inundate the computer with more (load of) programs.
These two crucial caveats also end up completely sabotaging any
performance boost the computers expect when installing self-generated
programs or those that receive the same from the extolled mentor-computers.
Because at the end of the day, a program is a program. Be it self-generated
or one bought or received as a gift from another. And in any and all manners,
a "fix" or "assistance" program ends up introducing more programs
and ghost-programs in the long run. In fact, the second cohort
of computers that look to tweak things at the OS level goes
through even more hassle. Because an OS (personality)
level tweak causes more system load and the need
for further downstream tweaks.
All these computers suffering the many
problems due to the load of their programs
("their life"), get so carried away with the problems,
that they fail to understand the (root) problem.
The problem is not other programs.
The problem is not the OS either.
The problem is not simple.
The problem is a few folds deep.
One, a computer needs an OS to function.
Two, an OS, seeing other computers will almost
innately get pulled towards having programs installed.
Three, the strong bond between the OS and the programs,
which as mentioned earlier, is permanent once a program is installed.
Four, because and thus, a new program (endeavor in work or relationship)
will always increase the perceived load of managing programs ("their life").
And thus, the rarest of the rare computers, seek something greater -
an ultimate release from the need to be a computer.
The ultimate release from the predicament of
being a computer and having to live
the life of one, is realizing the
Truth - that you are not "you",
that you are not a computer.
Concluded in part-3