Minor nitpick. His whole description about how "fluid information" works and how it's so much better than rigid/siloed hierarchy: Really it's tree-based vs tag

Minor nitpick. His whole description about how "fluid information" works and how it's so much better than rigid/siloed hierarchy: Really it's tree-based vs tag-based organization [1][2]. Tag-based organization turns the collection into a graph. Simple as that. IMO it's the superior way, since a graph is kinda like a superset of a tree, but there is nothing novel that was done by Roam here. You could have tag-based file systems too [3]. Note: when you have tags, it has to be capable of multiple-tags (not just one), otherwise it's not much different from a tree structure. [1] https://www.nayuki.io/page/designing-better-file-organization-around-tags-not-hierarchies https://www.nayuki.io/page/designing-better-file-organizatio... [2] https://zapier.com/blog/how-to-use-tags-and-labels/ https://zapier.com/blog/how-to-use-tags-and-labels/ [3] http://web.mit.edu/6.033/2011/wwwdocs/writing-samples/sbezek_dp1.pdf http://web.mit.edu/6.033/2011/wwwdocs/writing-samples/sbezek...