3 ms·
LISPs have this idea so deeply etched into them that code itself is data - homoiconicity. In the Clojure community, for example, you will find that the primacy
by MikeOfAu 7y ago
LISPs have this idea so deeply etched into them that code itself is data - homoiconicity.
In the Clojure community, for example, you will find that the primacy of data is well understood and used. Data-Oriented design and all that. You'll see the aphorism "Data is the ultimate in late binding" mentioned.
You will also find that it is immutable data that reigns supreme.
Notice also how, in a reactive system, it is the data (or the arrival of it) that coordinates the functions/processing, not the other way around.
I was exposed to the "data first" (and non-OO) way of thinking about 5 years ago, after being in the OO world since the mid-80s. I haven't looked back. When the penny drops for you on this it is a profound and liberating moment (or at least it was for me).
- hackits 7y agoThere was two competing viewpoints of OO. A object is nothing more than an animated data structure, and the opposing view saw objects as behaviors and you didn't map them explicitly to your data model. As most people viewed object's as simple extension over the data, it's not surprising to see most developer opt out for more basic form of data representation and that doesn't need object's at all.