rufuspollock
Joined 9 years ago
Joined 9 years ago
Strictly we could have titled this: the markdown database pattern for small personal databases.
The point was that for personal use e.g. keeping a list of projects, or books etc this is perfect. Or even for maintaining this list on a website.
It isn't for multiple simultaneous writes
Point on comparison with other formats is really well taken. I think the main argument i would have is ubiquity of markdown and markdown tooling.
We have this overall sense that "markdown is eating the world" in the sense that it is becoming a more and more ubiquitous and powerful format. What i would term "markdown plus" i.e. markdown plus extensions like frontmatter, wikilinks, typed backtick blocks you have something really pretty expressive - and add MDX and you have full JS(X) components.
At least, for reasonably small use cases (think under a 1000 items), this makes a collection of markdown files a great basis for a whole bunch of use cases from a document database to a PKM etc.
What we're trying to do here is set out the claims clearly (and atomically) and evaluate them in as transparent and honest a manner as possible. So far I've not seen this a lot on the internet despite the huge amount of material on this topic.
If you want to know more about motivation and approach there is quite a bit of detail on https://web3.lifeitself.us/about