In fact, I like to write notes and documentation in text form, and then I notice I have been using Markdown all along, so I rename my text file into .md, fix a couple of markers, and now it looks nice on a viewer that supports markdown, and I have syntax highlighting in my text editor.
When I'm reading Markdown, I almost don't even see the symbols. Beginning a statement with a # immediately just looks like a heading, surrounding a word with asterisks looks italic to me, wrapping a string with backticks looks like code formatting to me, and my assumptions are generally right so I don't need to render very often (which is why the Pandoc -> LaTeX -> PDF pipeline didn't bother me that much).
If I'm writing LaTeX or something, I generally have a very rough idea of what something will look like, but it's not terribly reliable for me. I need to render frequently because my assumptions about how something is going to look is likely to be wrong.
I mostly use Typst now because it is similar enough to Markdown, and the compilation time is so categorically faster that I see little reason not to use it, but I still respect the hell out of Markdown for popularizing this kind of syntax.
n.b.: the above quote is from The Matrix.
So why not Markup? At the time, everyone was using markup because Wikipedia was in wikimarkUP, with # for numbered lists, {} for macros and === to denominate titles. The latter still works in Markdown, but the former doesn’t. Funny heritage: Confluence shortcuts are also expressed in markup because it was the trend at the time, but they changed the shortcuts when they went to the Cloud.
Only just now has Windows Notepad been revised to render Markdown (I think it does now, anyway). And after searching for a Mac one I finally bought Marked. But that's all I could find. Otherwise you have to load MD files in some kind of editor and "preview" them. NO! I just want to double-click on the file and READ it, with the formatting applied. Why is that so hard?
Markdown is the intended rendering medium.
Try copying some markdown into these places:
- A reddit comment
- Microsoft Teams
- Slack
- Discord
- Google Docs
- Discord
- Notion
- Facebook Messenger (although only on desktop I think)
Etc.
Think about the word "preview." If you're "previewing" the Markdown file, what are you previewing its appearance in?
Gee, here's a Markdown file on my computer that I'd like to read (formatted as intended). Since I don't have a lightweight reader for Markdown, let me just...
1. Open it up in a text editor
2. Launch a browser
3. Navigate to some page that allows Markdown comments.
4. Log in to comment.
5. Find something to comment on.
6. Create and paste into a comment.
7. Post the comment.
8. Read.
SO EASY!
If you're on Windows it'll open in notepad.exe which is a markdown viewer.
On most flavors of Linux it'll open in a markdown viewer.
That leaves Apple and Android which I don't think have built in markdown viewers. But you can just install an app.
Respectfully, you've made some invalid assumptions. Even if your only use case is reading extant markdown, using Obsidian as your viewer probably still makes sense. Trivial, one-time config to open .md files in Read mode, and one-time system config to associate .md files with Obsidian, and voila: "double-click and read the damned file".
That said, if you were then to spend even a little time in Obsidian doing things other than reading, your "mystification" about "pointlessness" would vanish. Markdown is flexible and portable, eminently readable by machines and people (whether viewed raw or rendered), and Obsidian is an incredibly powerful tool for leveraging its capabilities.
Huh? Any open-source project on GitHub, at least, has the viewer right there. It's the default view of markdown files. I assume other repos are similar.
E.g. The readme https://github.com/jquery/jquery
And do you never actually clone the project to your machine and use it? When I sit down to actually use the project and I want to read the documentation, I want to double-click on the MD files and READ them. Not edit and preview, but read... with their intended formatting.
If you're looking at the code locally, what editor do you use that doesn't have a markdown viewer? I use Sublime with MarkdownLivePreview. Although honestly I generally don't, because md is so easy to read without a viewer.
It's officially only available for Linux (the Windows version is currently under development), and like I said, I don't use Apple products, and idk how familiar you are with manually compiling source code or how good Wine is on Macs, but maybe [Remarkable](https://remarkableapp.github.io/) could be an option?
Just thought I'd give my $2.70. ;)
Open a raw .md file in your browser and it'll automatically open in a side-by-side editor/preview. If viewing is all you want, you can set the default preview mode for markdown files to be fullscreen.
This is why I don't like proposals to make markdown a better markup language, I understand the intent, markdown sucks as a decent language, but these "improvements" make the plain text ugly, and that is most of the value of markdown lost right there.
I'm not proposing to make it a better markup language. I just want to VIEW it with the formatting that it calls for.
It's mystifying that people are actually opposed to this. It's like a massive psychology-class experiment, when a bunch of confederates champion an obviously-absurd point of view to see if the subject of the experiment will hold his ground.
Huh? If you find a markdown file in a project on Github, I have every confidence that it renders as intended in Github's markdown viewer.
And do you never actually clone the project to your machine and use it? When I sit down to actually use the project and I want to read the documentation, I want to double-click on the MD files and READ them. Not edit and preview, but read... with their intended formatting.
I like MacDown [1]. Someone recently forked it to MacDown 3000 [2].
The problem is that people want to use a web browser to display their documents, they want rich documents, and web browsers are awful at displaying text they don't understand the structure for. And <code> tags look consistently awful when read back, which is why we so strongly prefer syntax highlighting when we read XML or HTML.
Really, the big competition was BBCode, whose main problem is that it's too much like HTML, and Wikitext, whose main problem was that it's too bare-bones and domain-specific. The big advantages of Markdown are:
1. It's simply more readable. It pulls from how people were naturally formatting plain-text documents meant to be read as plain text rather than pulling from markup languages, so it more closely matches how people want to write documents in plain text. That makes the document easy to read while you're writing it. Asterisks for highlighting is an old convention, so were dashes and asterisks for bullets. Really, it made the asterisk an English punctuation mark for emphasis, which I think it genuinely is now.
2. It was easy to parse and short, which made it popular with Web 2.0 social media. It got picked up by Slashdot, Reddit, and Stack Overflow as "good enough" and "better than BBCode" for user generated content. Nobody liked using WYSIWYG editor boxes then, either. They were slow, buggy, and were often Flash-based before HTML5. They needed plain text formatting options, and BBCode was both annoyingly unnatural to type (just like HTML tags) and a little inflexible.
And nobody wanted to repeat MySpace and just let users use HTML. That was a horrible idea (Samy, XSS, etc.).
I think that is the biggest reason why Markdown doesn't support table. There are alternatives that do (e.g. wikitext) but they didn't get as popular as Markdown. Why? Perhaps it's because that tables will never really look fine in pure text no matter how clever your syntax is.
Isn't this a table?
|sn|name|
|--|--|
|1|George|
|2|John|
I feel like I've been doing this at least since about 2013?Edit: I get it now. It was not a part of the original spec.
|sn|name |
|--|------|
| 1|George|
| 2|John |
It can look better if we use fixed width font and add padding I guess?No doubt some janky one exists somewhere, but nobody uses that.
But perhaps it was the first big format that was followed a Unix-y "here's a CLI tool to go to HTML from this" thing, instead of some php script
Sure, but that's table stakes.
There are much better formats: AsciiDoc, reStructuredText, etc. Yet I also primarily use Markdown. I could use a format that's perhaps 20% better, and well-specified. But I'd have to use Markdown somewhere anyway. So I just stick with Markdown. It's good enough for me.
https://keenwrite.com/blog/2025/09/08/feature-matrix/
Are many features missing from the list? From what I can tell, objectively, plain text formats offer largely equivalent functionality.
Some text-based formats have more options for tables e.g. alignment of columns (it may help with numbers to right-align them) or multirow/multicolumn options. Some formats support definition lists (corresponds to <dl> in HTML) - a feature which I often find valuable but was not included in the original Markdown IIRC.
One advantage of using a text-based format is that it can be exported to either LaTeX or HTML and Markdown seems to prefer the HTML output by explicitly supporting inline HTML as an escape hatch for more complex constructs (e.g. tables with rowspan/colspan). In addition to often not being supported for a non-HTML export-type it also hurts the WYSIWYG experience when reading the file like plain text.
I think if you define "better" as having well-defined extensibility to enable multiple implementations (i.e. not ad-hoc things pandoc lets you do), then rst (which can be transformed into XML as per https://docutils.sourceforge.io/docs/ref/doctree.html) would be "better" than markdown.
Also I like the WYSIWYG feature of Markdown where it has an advantage over the traditional Markup languages like HTML, LaTeX, groff etc. of being easier to read in the text file. Dedicated syntax highlighting can go a long way to make markup easier to read, though.
The question is more why Markdown is slowly but surely outcompeting them.
Markdown is fundamentally WYSIWYG - you edit something and you get it rendered 1 to 1. Either in plain text (a.k.a. "source") or when it converted to HTML/CSS and then presented.
WYSIWYG requires 1:1 mapping between "source" and "presentation". Markdown is exactly that. While HTML/CSS is 1:N mapping - same presentation can be achieved with many combinations of HTML/CSS rules. That's why "true WYSIWYG" is barely achievable with HTML/CSS.
Simple and Universal: A History of Plain Text, and Why It Matters
https://amontalenti.com/2016/06/11/simple-and-universal-a-hi...
You might enjoy it!
If you only use headlines and bulletpoints, I have a very pleasing result for a simple text file.
reason #3 Markdown succeeded: Built on behaviors that already existed. It succeeded because it came from the culture it was born in. Email formatting conventions. HTML. Plain text.
No format/vendor lock-in and very amenable to living in a git repo. For my note taking that's already game over right there against everything else. I don't want to worry about whatever cursed format OneNote uses is still something I can extract in 2035.
I also like that it's become a defacto standard that LLMs speak. I can tell it to look at the code in this server repo and make me a API_documentation.md and it'll grasp that I want a text based summary of how to use this endpoint