Yup. I wonder how much this talk influenced Next's NeXTSTEP design? Certainly a lot of the things he was thinking about have been solved in a fairly elegant manner - late-binding, delegates that implement mappings, reflection, using protocols instead of class hierarchies where appropriate...
Actually, when you get down to it, MVC is all about making client specific mappings for the loading of data into views. The talk is not exactly startling seen from a 2011 perspective, but it's nice to see the reasoning behind so many of today's patterns so clearly expounded.
Actually, when you get down to it, MVC is all about making client specific mappings for the loading of data into views. The talk is not exactly startling seen from a 2011 perspective, but it's nice to see the reasoning behind so many of today's patterns so clearly expounded.