To better organize complex tags, to better handle large domains. Yes, doing OOP in scripts , fleeting applications, simple, is not advantageous. But luckily many people do not do OOP in these things, although they say they do.
OOP is modinha if you consider that people use where they should not. Modinha is not something fleeting, it is something that is only being used because people use it without a clear reason. It is not modinha when used where it is useful. It is very modinha when the person talks about what he is doing and is not even there, she just wants to be part of the group that is" drowning ". And as I said in previous answer , it's teenage sex.
The creation of OOP does not have anything modinha. Most technologies are not modinhas. The same can not be said of several methodologies that were even created to meet a need, but do not fulfill the promise .
It's like carrying a gun, just to take an example. He is useful, but defending that everyone should be able to have a gun is modinha. It does not meet a real need.
In general PHP is modinha. You have a case that is not, but it is rare. And honestly when it is, it's usually the wrong language. PHP is more languages than script that exists, so how to name variable indicates this. Put OOP in PHP was and still is modinha. Of course the most precise definition of this is survival . Today few things need scripts , the bulk of development are on top of complex things. Without OOP the language would deplete a very small niche, which happened to Perl. But then the language was inconsistent.
OOP is much harder to understand and do right, so much so that everyone does it wrong. It's very common for people to complicate your design to try to be OOP without any advantage.
OOP is great in these cases of many relationships between objects, when objects are very complex, when there are subtype relations, hierarchies. GUI benefits a lot from this. Games usually benefit, some types of business. Frameworks and more complex libraries can benefit greatly.
OOP can be great for maintaining domains that tend to change a lot and are more about business rules than mechanisms, although mechanisms can benefit as well.
I reinforce that the answer says that OOP and PE are very different things. I would like everyone to read the links there to understand a little more about OOP (I know I did not answer fully) and understand that structured programming is something very simple and focuses on another aspect of OOP programming that does not focus . structured programming is not about code organization, it's about algorithm flow.
