Googles long term problem is its basically flawed cloud network model.
This embryonic cloud based noosphere we all call the internet is just a
single instance of a general class of processes that have been called
COMPLEX LIVING SYSTEMS. After millions of years of statistical trial an
error nature has blazed the trail to demonstrate the recurring themes
that appear to be mandatory for successful homeostasis in such
systems. With out going into a long song and dance about these
recurring mandatory attributes, I will simple beg that you temporarily
humor me by accepting the following as one of these mandatory
attributes. COMPLEX LIVING SYSTEMS utilize distributed redundancy of
function as their key defense against the inevitable errors that arise out
of massive complexity. Every LIVING CELL carries the complete DNA
methods blueprint plus historical fall back DNA. Every INDIVIDUAL
ORGANISM in a species carries the complete repertoire of
environmental interactive attributes and abilities(methods). Even at the
simpler atomic level every atom contain, internal to itself, all the
methods required to behave and recombine repeatably as a member of
its class should. None of the above individual members of a class must
check back with the mother ship to access its behavioral methods. They
are all locally redundant.
Back to Googles flawed Cloud Network Model.
Sooner or lated the evolution of network computing models will return
to this time tested strategic necessity. This means in the context of
cloud computing that each user node must keep all its methods and
data structures locally self contained so as to support independent,
organic, recombinant, evolutionary possibilities separate from those
enforced by a central mother ship repository of acceptable methods.
The user nodes can self operate when not connected. The user nodes
can move their complete methods & data set realities to another
mother ship server at will. The user nodes can reassemble a mother
ship's data and methods central repository as an ultimate backup to
catastrophe. This in no way precludes the user nodes from choosing to
update and synchronize their methods and/or local data sets with the
central cloud mother ship either automatically or manually. Local
autonomy of methods and data sets also offer the choice to keep local
versioning of methods and data sets as a fall back autonomy insurance
strategy. I could go on but I am sure you tire! I know I do.
Anyway - here is where both Apple and Microsoft have a long term
serious advantage over Google OS. They have deep and wide OS tools
that can support this necessity to maintain a strategy of distributed
autonomous methods and data sets. A strategy nature historically
seems to indicate is the proven path to creating STABLE COMPLEX
LIVING SYSTEMS. No non-compliant systems get out alive.
Oh - One last thing!
I am not particularly a Microsoft fan but we should not count them out.
With new more visionary leadership they could be a serious contender.
They have a large talented team and a very valuable store of intellectual
capital. A serious three way race would be the Holy Trinity of
competitive innovation.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
