3 ms·

I briefly thought about the beginnings of this after looking at KVC. I pondered the dots vs slashes question, what a query would look like, and whether every ob

I briefly thought about the beginnings of this after looking at KVC. I pondered the dots vs slashes question, what a query would look like, and whether every object in a process could have a name. Fun to think about, but that is as far as I got. You have taken this much further.

mpweiher 8y ago
:-) The problem with something like KVC is that you then have to lift everything into this new "KVC language", which is embedded as strings in the main programming language. Which then gets you to dictionary-oriented programming (Xcode, I'm looking at you) and that's really quite painful. While doing performance work at Apple, I though about forming an association called DUKE, Developers United against Keyed Everything :-) On the other hand, there obviously is a lot of benefit to KVC and KVC-like mechanisms, because we keep re-inventing them everywhere and all the time. I myself had done so with the BBC project that led me to in-process REST. And at one point it just clicked: language support for URIs, and URIs really are universal, so we don't need any other identifiers.