"In an OOPL data type definitions belong to objects. So I can’t find all the data type definition in one place. In Erlang or C I can define all my data types in

"In an OOPL data type definitions belong to objects. So I can’t find all the data type definition in one place. In Erlang or C I can define all my data types in a single include file or data dictionary. In an OOPL I can’t - the data type definitions are spread out all over the place." To me, this is the main argument. In many cases, I think we can go even further, defining the entire data model in SQL, letting it be the single source of truth on what the data model is, letting all code outside of the database adhere to it. The inverse of an ORM.