How the pattern of public, communal, and private property appear in programs.

Often, compiled programs have extra code added by a compiler to ensure their local variables are not modified outside of the program's environment. This behavior is eerily similar to how the capitalist state uses their security forces to ensure the existence of private property in their economy.

However, commonly local code can become redundant; so humans have grouped them into namespaces. Namespaces seem similar to communal property; where a tribe collectively owns the property.

Eventually, some communally owned code gets used enough by communities for them to end up publicly owned. This is similar to how communally owned objects lose ownership and can be used by anyone.

• The programming example would be adding commonly used functions in programs to a standard compiler or interpreter.