Why exactly is OOP bad? When should we use it?

Question

I know it's mostly about hiding complex code, and unnecesarry encapsulation, but i'm not really sure. How exactly is OOP seen by C#? Is it more efficient?

Answer 1

OOP isnt really bad in itself. It is meant for thinking about programming in terms of something the human brain is familiar with: objects, their properties and behaviors. It is built upon existing procedural programming concepts so it isnt too different anyway. It is great for large amounts of data that can be broken up into different categories. Building a game is a good way to implement OOP features by thinking of characters and items as objects, and using methods to change their properties and express behaviors. Also, you can easily apply this concept to something more mundane like a database interface. C# is built to handle objects as it is a very class based language.