|
|
|
|
|
by beders
2804 days ago
|
|
> Except for the fact that objects can be serialized and ORM's exist to convert your data into OOP. Except for the fact that there's usually a mismatch between how your database handles data and how you want to get them back into objects. Cue: Object-relational impedance mismatch. And while your objects become bigger and bigger and your domain more complicated, you end up relying on ORMs who keep re-creating those objects from the database with every transaction and are loading lots of data no one requested.
And then you are wondering why your stuff doesn't scale. > Interfaces are essentially stripped down abstract classes. How this is not a subset of OOP, I don't know.
It's not. Interfaces have been around way before OO entered the field. |
|