ECS (data-oriented programming?) is slowly taking over in the video game industry as a clearly superior paradigm. i did some UE4 programming recently, and as powerful as that engine is, the super-heavyweight object/inheritance system was the source of almost all unnecessary complexity i dealt with

Even then, from what I've heard the trend is turning sharply away from inheritance and towards composition of components and systems. Maybe you could argue that that's still OOP, but it's not what most people mean by the term these days

Personally, when I think of OOP, I think of objects which combine state and the code to modify that state.

The details of how it’s implemented - inheritance vs. composition - strikes me as more of an implementation detail than a vital difference.

ECS, the emerging game pattern, breaks off the state-modification code as well

Agreed, never understood the appeal for something like web applications but as soon as I tried game Dev it feels like the perfect fit for lots of entities with their own internal state.

There are many enterprise web applications that have large amounts of internal state, so I think OOP techniques work relatively well there.

Game programming is a lot more fun though.

Very well architected OOP is fantastic to work with/read on any moderately complex application. The problem is very few people know how to architect an application well, regardless of OOP or not.

OOP should be applied to a specific domain, namely GUI and video games.

In other cases it's a meh.

I was under the impression OOP with classes is not cache performant when doing common game engine tasks like mass updating the velocity or position of objects.