3
There is a fundamental misunderstanding when you oppose OOD and MVC.
MVC emerged in the area OOP and more precisely in a Smalltalk environment.
The separation of responsibilities between objects in the MVC pattern is in fact meant to improve the encapsulation and the clean collaboration between objects in a complex system, not to get rid of them.
Well ...
3
OO
Can be done regardless.
Even MVC is an OO design pattern, first introduced by SmallTalk a pure OO language.
Unless we are talking about a language such as JavaScript, most languages support a tightly packed data structure. So doing something OO isn't going to impact on memory efficiency very much.
A few caveats emerge when you introduce flexibility like ...
1
Your assumption that you have to have an object for each ip camera if you do OOP does not hold. Also, you seem to be assuming that ip camera objects needs to hold the data associated with them at all times or that every ip camera object has to be present at all times, this is also not true.
I know this is unfortunately what OO looks like in many projects, ...
Only top voted, non community-wiki answers of a minimum length are eligible
