Things Don't Move -- Summation

Conceptual Things don't need or even want to move in a virtual world to get things done like real things in the physical world.  Conceptual things only pass messages to other Conceptual things asking them to do something internally in their fixed place in a virtual world.

When we impose our view on Conceptual Things in a computer based information system that they "move" or must move to get things done in a virtual system world then we tie ourselves to way of thinking, an approach to the problem, that handicaps the solution.  In general millions of years of human evolution have in my opinion predisposed a general predominate trait to focus on action of a physical thing to understand it, control it and manage it.

The information age focuses on the abstracted conceptual nature of a thing to understand and manage it independent but related to is physical nature because that is what the information age is all about.  The separation of the physical properties and behavior of things from their conceptual logical properties and behaviors. 

We are handicapped by our social view that a primary tool of our society, money, moves.  We are still bound to the beginning concept of money moving hand to hand that became money moving account to account as representational conceptual abstracts of hands.  The biggest hurtle we now face is to change our conceptual view of money to something that "is" as a virtual object that does not move.

This handicap is overcome in the virtual object oriented world of the information age when:

Money is viewed as an object that does not move. 

Account is viewed as an object that does not move.

Each is uniquely identified as an instance of a their class

They each just pass messages between them.

Movement is the message. 

The message is the movement. 

The messages between Money and Account are the only "things" that move. 

A specific message from a unique instance of all Users to their unique and associated instance of Account to do something and a message from the unique Account to each unique instance of Money associated with that unique Account to do something and a response back from Money to Account to User that the request was completed is the architecture of the digital monetary object oriented system model.