4 ms·
The author misunderstands schizophrenia and I don't think they understand what OOP brings to the table. Using objects in your design makes your code easier to
by samsquire 5y ago
The author misunderstands schizophrenia and I don't think they understand what OOP brings to the table.
Using objects in your design makes your code easier to understand. Using objects does not prevent you from using data oriented architecture.
OOP is better than having lots of global functions that operate on data. It organises your data and code together. It makes APIs easier to use. Call a function, get a response, call functions on response object. It layers your API ordering and makes them inherently understandable. At least good OOP does.
Nowhere in this article prevents you from using objects.
https://en.wikipedia.org/wiki/AoS_and_SoA https://en.wikipedia.org/wiki/AoS_and_SoA
- dvfjsdhgfv 5y ago> OOP is better than having lots of global functions that operate on data. "Lots of global functions" is not the only alternative though.
- Gibbon1 5y agoIf your solution is a data oriented pipeline, OOP I think just gets in the way.
- bluefirebrand 5y ago> Using objects in your design makes your code easier to understand To a point. Past a certain tipping point I find OOP programs become extremely over-abstracted and bloated with way-too-much boilerplate, to the point where it becomes very difficult to work on.