This is a good point, I agree.
> As for the knowledge base features, however, I'm still far from being able to reproduce the speed and precision of recall that I had on InfoSelect, or even Evernote with a solid tag hierarchy. I also use Dynalist to have an outliner on mobile.
What speed and precision are you missing? It seems that org mode should have the capacity to establish any content connection scheme you could dream up.
> KB situations
What does KB mean?
> I would also love to be able to browse connections in my knowledge base, TheBrain-style, but that will always be clunky to unusable on a pure-text UI.
I don't think this is true. Depending on the kinds of connections you want to browse in your knowledge base there are plenty of ways to transform the ui to show them. That is what I see org mode to be at it's essence, a software tool to allow for transformations of text on screens. I think though, that your point is more about browsing. We should have text-based ui browsers for connections. All a gui like the brain is doing is putting animations and a mouse on top, we can definitely specify things via the keyboard in a number of ways to replace the mouse, and who wants animations to begin with? If the main pull at the end of the day is that GUIs are pretty and text UIs aren't then let me point you here [1].
[1]: https://lepisma.github.io/2017/10/28/ricing-org-mode/index.h...