Block reference

@Klaas Thank you for sharing your perspective. I would like to offer another point of view.

I am less interested in making Obsidian a clone of Roam - or any other tool - and more interested in having features that make my process of thinking and reflecting better. With that said, Roam is only mentioned in this thread because they have a pretty strong implementation of block reference. Notion also has a good one, although not as strong. Coda has a very good implementation, but it looks and feels more like a database record than a document block. From these three implementations of a quite useful feature for the purpose I listed above, Roam has it better. Hence the reference to it.

I don’t see why we should leave at it. Giving up implementing something because it is not simple doesn’t seem to me a good reason at all. Au contraire! The more complicated the better, for analyzing and improving complicated processes can provide great return in terms of efficiency.

I agree Obsidian is a fantastic tool and I agree that it has many features other note-taking apps do not offer. But why should we give up (asking for) new features that can make it even better? This is the space the development team set for this very purpose.

I’d love to hear from the community any use cases or design proposals for this feature. If there are strong reasons not to implement it, I’d love to hear them as well. I just don’t think the push backs so far are enough to shoot down the feature request.

7 Likes