If OOP makes problems with large projects, what doesn't?
Posted
by osca
on Stack Overflow
See other posts from Stack Overflow
or by osca
Published on 2010-04-11T22:19:07Z
Indexed on
2010/04/11
22:23 UTC
Read the original article
Hit count: 278
I learned Python OOP at school. My (good in theory, bad in practice) informatics told us about how good OOP was for any purpose; Even/Especially for large projects.
Now I don't have any experience with teamwork in software development (what a pity, I'd like to program in a team) and I don't know anything about scaling and large projects either.
Since some time I'm reading more and more about that object-oriented programming has (many) disadvantages when it comes to really big and important projects/systems.
I got a bit confused by that as I always thought that OOP helped you keep large amounts of code clean and structured.
- Now why should OOP be problematic in large projects?
- If it is, what would be better? Functional, Declarative/Imperative?
© Stack Overflow or respective owner