4 ms·
The main problem with objects is the proliferation of conceptual entities that increase complexity instead of reducing it. This was in full display with the cre
by coliveira 5y ago
The main problem with objects is the proliferation of conceptual entities that increase complexity instead of reducing it. This was in full display with the creation of design patterns, which introduced a large number of concepts meant to simplify programming, but that in fact multiplied the number of classes in an exponential way sometimes without improving understanding. Sometimes you'll have better code by just removing the crutch, but OO languages are designed to favor this kind of approach.
- throw_m239339 5y ago"design patterns" are mostly here to make up for the flaws of Java or C++. For instance, there is no need for factories classes when a language supports passing functions as arguments of other functions and closures. I say mostly, because something like the Observer pattern is still useful even outside OO. It's also a way to communicate an intent or a role a certain class has. I think all the SOLID/DRY/Clean code concepts were more harmful to development in general than design patterns, because these ideals became an obsession.
- jcelerier 5y ago> For instance, there is no need for factories classes when a language supports passing functions as arguments of other functions and closures. C++ supports passing functions as arguments and closures yet factories are often necessary, how else are you creating new objects from dynamically loaded plug-ins ?
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]