* The sweet spot is to use OOP only when needed. * Abstract your core functions to the max Here is a real life example. I write a software which is based mo

* The sweet spot is to use OOP only when needed. * Abstract your core functions to the max Here is a real life example. I write a software which is based mostly on functions. A php based CMS If you look at it from aside, you will say its huge and probably needs a lot of code (and objects). The truth is that the core set of functions are less than 20 and less than 100K of code. If you write your functions well, you don't need OOP and you will have - less code - less memory usage (functions free memory after run) - less problems