*TRUE* OOP and Other Paradigms

[A-Man]

I'm not sure if it's just me being oblivious of this for so long until now, but lately, it seems there has been a greater number of people bashing the OOP style. I don't often involve myself into such discussion, but this one time I did say that OOP works better for games (I know because I've tried imperative for games, and things get messy rather quickly). So the discussion went on for a couple of posts, until one came up and said "but that's only because what you use is not "TRUE" OOP. That was when I thought that maybe I'd be talking out of turn if I continue arguing any further.

So yes, what is true OOP anyway? What do you think of OOP in general, and what do you say of the "single responsibility principle"? The latter, in my opinion, might be sort of extreme and not practical. Would not strictly following it mean that you're not doing OOP?

What are your thoughts on functional programming, also? I like it, even though I don't see how one can write an entire program with that if the program isn't a one-liner. I'm quite surprised to see people trying to enforce sticking to one style throughout. Why not mix as necessary?