My original description of what it is still stands: “Markdown is a text-to-HTML conversion tool for web writers.
Yes, that's how John Gruber defines it. But like every creation you share with others, it can evolve. If popular, it will evolve. People create their own versions and uses and intentions with it.
I've used markdown for 12 years or so, for two reasons:
1. As a way to write plain text but still get visual layout cues without using a proprietary format/tool (e.g., Word).
2. Have options for later conversion to other formats/outputs (for Gruber, HTML.)
So for me, writing markdown on my Apple device means that instead of using Apple's proprietary format, I have another place to write plain text markdown and use/share it elsewhere (which I often do).
Gruber is Markdown's father but the overall Markdown community has stopped listening to him a long time ago. Doesn't help that he hasn't fixed the bugs in his Perl script since 2004.
Indeed. His post says:
It’s trivial to create malformed Markdown syntax
That's because his specification is loose, and there are no test-cases nor updates to clarify ambiguities.