Less is exponentially more
One of the authors of the go language talks about its origins and why a language that was designed by C++ programmers to replace C++ programmers does not actually attract C++ programmers.
The answer can be summarized like this: Do you think less is more, or less is less?
For the go authors, less is more. By removing various power features of C++ that were also overly complicated, it made the go language both easier to use and ultimately more capable as a consequence.
An irony is that the author explicitly talks about composition over inheritance as the tradeoff that go made to simplify the language. This is the exact opposite tradeoff that we made at Dendron, favoring inheritance (aka hierarchies) over composition (aka tags).
Even if the technical details took opposite turns, we made the decision to focus on hierarchies precisely because it would simplify the retrieval process. Tags made it possible for any note to be categorized as anything. Having a canonical hierarchy limited people to having one canonical place for a note but its precisely this limitation that makes Dendron scale for large knowledge bases. ac
Backlinks