> However, not using strictly defined self-contained data types for a large project is also recipe for confusion and pain. Not using well defined data types fo

> However, not using strictly defined self-contained data types for a large project is also recipe for confusion and pain. Not using well defined data types for in a widely exposed interface in a large project is suboptimal. Overly formalizing data types for entities of limited scope is suboptimal on small and large projects. We need to be careful about adding unnecessary weight to large projects, because it costs more there. > in many languages arrays are objects, dictionaries are objects, and tuples are objects I am not aware of a canonical definition of object. One thing that is commonly included is the idea that objects have identity. So "two" arrays with the same values are distinguished in the object world. This is not what people mean if they create an RGB from an array (or dictionary).