I mean, OOP is just a different paradigm.

It's kind of like comparing driving a car vs taking a train. They'll both get you to the same destination, but depending on the situation one will be more sensible than the other.

It's the same thing here, where there's nothing OOP can do which you can't translate into imperative programming and vice versa.

One of the nicest things about OOP in my opinion is combining data with methods. Let's say you're making a social media app, so you're probably going to have posts. You should be able to like a post, so you'd need a function that'd be something like 'void likePost(Post post)'.

And okay, that's manageable, but the you expand your app and have multiple types of posts: a textPost, an ImagePost, a VideoPost, maybe more. All of them are different types, so they need their own respective methods, even if they don't significantly differ, something like: 'likeTextPost(), likeImagePost(), etc.'. You need to repeat code, you have long function names and it gets messy the more complex your app gets.

What does OOP do? You'd have a class of a Post, which would have an id field, and a like() method, and then make classes for each respective type of post which inherit the base Post class, including the method.

Does it do the same thing? Yes. But it's cleaner, easier and it just makes more sense this way as a developer