3 ms·
> I think even FRP (as pure data flow as we get) is hierarchical since components (and sub-components) can still encapsulate state. That's an interesting point
by jamii 12y ago
> I think even FRP (as pure data flow as we get) is hierarchical since components (and sub-components) can still encapsulate state.
That's an interesting point. We explicitly avoid encapsulating state in that way, preferring views to interfaces.
> I would argue that relational is also effectively hierarchical ... object graph.
A graph is fine. The difference from a typical OO hierarchy is we get to start wherever we want in the graph and we can easily insert new edges anywhere in the graph, or hyperedges that relate multiple entities. It's not like a filesystem where you have to decide which property of the file is most important and gets to be at the top of the hierarchy.
- seanmcdirmid 12y ago> A graph is fine. The difference from a typical OO hierarchy is we get to start wherever we want in the graph and we can easily insert new edges anywhere in the graph, or hyperedges that relate multiple entities. It's not like a filesystem where you have to decide which property of the file is most important and gets to be at the top of the hierarchy. Objects support references that give you pretty much the same thing. The ability to add new kinds of edges is more of a function of your object system. In a dynamic language where members are basically defined as a dictionary, you just add a new key-value pair to the dictionary.