Yes! Someone gets it – “It has always been an unfortunate characteristic of using classes for application domain information that it resulted in information being hidden behind class-specific micro-languages, e.g. even the seemingly harmless employee.getName() is a custom interface to data. Putting information in such classes is a problem, much like having every book being written in a different language would be a problem. You can no longer take a generic approach to information processing. This results in an explosion of needless specificity, and a dearth of reuse.”
–Rich Hickey, http://clojure.org/datatypes
Data is just data. Please, coders – free the data from all those bureaucratic OO controls on it, and just expose the rules if any, let us obey them thoughtfully our own way. It has got to be better than all these little bureaucratic fiefdoms exerting paranoiac control over their bits of data.
Ok, so it sounds good…now to finish the clojure koans, having realized that the ___ construct is just where you put your answers and not a new triple-underscore special variable. But I’m also hacking on a larger clojure app while learning the basic syntax…it really does seem promising…