OOP *is not* (even primarily) about inheritance; it’s about message-passing. If your programming paradigm supports sending messages to an arbitrary receiver, with a protocol for what to do when the recipient does not respond to that message, then you have object-oriented programming. Encapsulation, polymorphism, inheritance, etc, are simply logical extensions of the basic message-passing (and -responding) architectural feature.

But yes, inheritance is the evil spawn of laziness; it was taught as the “foundation” of OOP from the ’80s through (at least) the mid-’90s, and has grievously warped millions of well-meaning developers’ abilities.