This organization of language in this fashion is English-specific though. I wonder what feels intuitive to non-English (or non-Romantic) speakers - is it OO as well, or something else?
Edit: https://en.wikipedia.org/wiki/Verb%E2%80%93subject%E2%80%93o... Cool.
"The table is red."
and
"Red is the color of the table."
water.heat(stove);
because it's the water that's being changed and change should be encapsulated. On the other hand, the stove may also change in the process. In fact, the water and the stove do things to each other. Then what makes either of the two options more appropriate? Similar issues arise with a method called sendMessage; is the object having this method now supposed to send a message or to receive a message?heatingStrategy.heat(water, stove);
While I'm no fan of OO as a dogmatic solution to every problem, the differences between it and any other reasonable approach are small for most problems, compared to the complexity of solving the problem itself.
Hackers hate this, because small segments of code that look near-identical can do vastly different or complex things and lots can go wrong in there. Also, the higher you go in abstraction, the more subtle the code becomes, the more important differences in meaning originate from very small differences in source code. Take a haskell monad chain and try to explain the sequence of 2 statements ... it takes 2 minutes of thought to figure it out. But of course those 2 statements do much more than 100 lines of C can do.
And of course bad programmers hate this, because you have to learn abstractions.
It depends on what you're doing. If you're writing a big application, something to be supported over the long term that isn't trivial, then OO is most definitely the way to go. If you're hacking something together that won't last the week, raising abstraction level will only stand in your way. If you're planning to rewrite the core of the application on a monthly basis, OO, and any other kind of abstraction, will make life very hard on you.
"The stove heats the water." An object performing an action on another object (a direct object, in parts of speech), changing the state of the direct object.
So when we code this, it makes sense naturally to write something that is readable in human terms:
This makes code easier to reason about and easier to go back to later. Hopefully, our code reads like the computer- and human-readable literature it is.