> I don't believe that the problem is OO in itself, but the way in which it is often used. That's similar to what proponents of communism have been saying - "i

> I don't believe that the problem is OO in itself, but the way in which it is often used. That's similar to what proponents of communism have been saying - "it does work if you do it right". The problem is that things start breaking down as soon as the project scale. For small programs a pure OO model can work, but increased complexity means people will definitely switch to a hybrid OO-(procedural|functional) style, simply because pure OO is untenable in large codebases.