%% date:: [[2024-01-24]] parent:: %% # [[Criticisms of Markdown]] Here are some criticisms of [[obsidian-playbook/Using Obsidian/02 Making Notes in Obsidian/Markdown|Markdown]]. ### Its features are limited Markdown's simplicity comes at the cost of considerable compromises in terms of features. Some formatting, such as tables, are notoriously more fiddly to implement in Markdown than other markup languages. Markdown also has no conditional logic. ### It is not standardized There are no formalized standards for Markdown, so many formats have emerged: - [[GitHub]] Flavored Markdown - [[MultiMarkdown]] - [[Markdown Extra]] - [[CommonMark]] The lack of standards also creates cross-compatibility issues between Markdown editors. For example, [[Roam Research]], [[Notion]], and [[Obsidian]] all use Markdown, but the content is not easily usable across the three of them without significant reformatting because each app implements Markdown slightly differently. ### It opens the gate for dilution Markdown typically accepts HTML to make up for some shortcomings it has, feature-wise, but this goes against the original purpose of a markup language: to separate the actual content from the site created from the content. ## [[Online Markdown text editors]] ## Local Markdown-based text editors - [[Obsidian]] - [[Bear]] - [[Ulysses]]