2025–03–14
1403/12/24
ANNO·VICESIMO·NONO·DIE·SEXAGESIMO·QVINTO·VITÆ·POVYA
I’m missing Zea already.
In rich organizations, tools are merely a temporary thing, they are easily replaced and purchased. In poor places they are repaired, bought with lots of money savings and after loss of decision making. It is thus those places that make a huge connection with the tools, either get stuck, or understand it so well they prevail.
![What about a tree-structured language?
So let's say we are crazy and want to take ideas of LISP too far. What if we have the whole language and data in one gigantic data structure that we can see and modify:
[A diagram of a tree structure labeled 'Program' at the top. It branches down into several nodes: 'sum' which leads to 'func(x, y)' and an addition operation on 'x' and 'y'; 'main' which leads to 'func()' and 'sum(b, 2)'; and variables 'b' (with value 2) and 'a' (with value 3). Dotted red lines represent Nelsonian (Ted Nelson ✦) 'Visible Links' connecting various parts of the code and data across the tree.]
The biggest idea here is: What if the whole structure gets changed as it runs?
One lovely idea here is to have Nelsonian (Ted Nelson ✦) 'Visible Links' in the structure.
P.S. I just jot down the idea. I know it looks ugly.](/photographs/thoughts/2025/03/14/artifact-80425f2be7984da2368fb4327ec6572d.webp)
A Language And Database In A Live Tree Structure
Day's Context