> Classes are the the creation of complexity by unnecessarily fusing code with data. No, classes discourage unnecessary complexity by fusing code with data --

> Classes are the the creation of complexity by unnecessarily fusing code with data. No, classes discourage unnecessary complexity by fusing code with data -- leading to a better separation of concerns. In the end, the question is about how to split up a software into components. Should "data" and "business logic" be separate modules or shouldn't it rather be (for example) "accounting" and "hr"?