What should be the TOE and what not?

Question

I read a lot of people saying that some things should not be written in an object-oriented style - like a person learning the OO style coming from background C, what do they mean by that?

What shouldn't be OO, why are some things better for this design, and how do we know when it's best to do something?

Answer 1

The real world is full of objects.

It is useful to make the software world fit the real world.

"What about the" system utilities? They only deal with abstractions, such as sockets, processes, and file systems. " They sound like things to me. They have attributes and behavior, they have associations.

proof, OO , . , . , . , , - , .

OO, , . OO - , . , , , , OO. , . , , " ".

Answer 2

, , . . , .

OO , . , , , , .

OO - , , , . : ( ) , , . , , , .

OO MVC , , , , , , , . , -, OO " "... , , .

Answer 3

- - . OO , , , , .

, , , .

Answer 4

( ?), OO .

, , . , , , Visual Studio Unrefactor, .

Answer 5

. Reflector , dll.NET framework . , ++ OO, .

Answer 6

( , .NET mobile), -OO, . , , , , , . .

Answer 7

: "", , , .