3 ms·
If by "abstraction" you mean ADTs - of course there are some (not many) places where they are useful. And you can easily have them or change to them later. It'
by jstimpfle 10y ago
If by "abstraction" you mean ADTs - of course there are some (not many) places where they are useful.
And you can easily have them or change to them later. It's just another few lines of boilerplate to make a few method tables. But I don't like to have the implementation logic in the places where method dicts are wired, especially for interfaces with very little coherency, like GameModel3d: render, click, contextString, serialize... Doing that instead of aspect-oriented is a violation of the "separation of concerns" principle.
- tcbawo 10y agoIsn't the dream of a reflection library to build serialization using an Observer pattern, where the serialization logic is unbounded and business logic never mixes? It would be great if the standard came up with something that would be so broadly useful and allow developers to focus on their domain instead of serialization.