Classes aren't necessary* for OO. Inheritance isn't necessary, either (and probably causes as many problems as it fixes). Late-binding via message-passing pret

Classes aren't necessary* for OO. Inheritance isn't necessary, either (and probably causes as many problems as it fixes). Late-binding via message-passing pretty much covers it, IMHO. Structure code as a group of autonomous actors communicating by passing messages according to agreed-upon protocols, and each (polymorphically) chooses how to react to them. Erlang implements that model with unusual clarity, IMHO. * Neither are prototypes.