That's pretty interesting since you are highlighting the multifaceted aspect of OOP: it can be used in a lot of way (and I only showed the basics ones), but oftentimes libraries and frameworks are kind of enforcing a specific one. I think it's a good thing to do when creating a library/framework since handling all the possible use cases is impossible, and it's also a benefit when you are using the library/framework since it's guiding your thoughts to create uniformised code.
That's pretty interesting since you are highlighting the multifaceted aspect of OOP: it can be used in a lot of way (and I only showed the basics ones), but oftentimes libraries and frameworks are kind of enforcing a specific one. I think it's a good thing to do when creating a library/framework since handling all the possible use cases is impossible, and it's also a benefit when you are using the library/framework since it's guiding your thoughts to create uniformised code.
You are right. Well said!