3 ms·
This brings back thoughts I've had that we should be working with normalized data in code, rather than thick objects. I think the main reason we don't is becaus
by nadagast 6y ago
This brings back thoughts I've had that we should be working with normalized data in code, rather than thick objects. I think the main reason we don't is because there's a lack of tooling around it in our languages. I think a system/language/library designed around this could solve some of the problems in the article as well. First class support for having only one value for a given domain specific id, relations, declaratively describing constraints, and strong querying seem like they would be very helpful to lots of programming problems in complex apps.