4 ms·

Amateur question: Why can´t browsers just fetch a markdown file and render its html representation? (is this what the article implies?)

dom0 10y ago
Because there are dozens of more or less incompatible markdown dialects.
verandaguy 10y ago
Browsers implement well-defined web standards, which Markdown unfortunately isn't. The original author, John Gruber (of daringfireball.net), hasn't been too supportive of having a single, fixed Markdown standard, and this has resulted in spinoffs with various syntaxes and features: - GitHub-flavoured Markdown - CommonMark - etc... On top of that, there isn't even some meta-standard which would allow hashbang-style preambles/doctype declarations to determine which version of Markdown is being served. So, between the fact that there's no fixed de-facto standard and no de jure standard syntax or feature set recognized by any of the major standards bodies (IETF being one of these), it would be impractical for browser vendors to implement support for Markdown. Finally, the standards that browsers implement take time both while being defined, as well as while being implemented; these are things that will be seen by billions of people worldwide, and there's extremely little room for error, so revisions are always necessary at every stage in development. For example, work on HTML5 can be traced back as far as 2004, meaning that from inception to release, development took about a decade.
- Ajedi32 10y ago
  Couldn't they just adopt CommonMark? That flavor already has a complete spec and test suite, and is specifically designed to be as compatible with existing implementations as possible. I believe the only thing really missing is for more of the community to start rallying around the standard.
  - verandaguy 10y ago
    Community engagement's a big part of it, though. I can define my own, extremely thorough and well-documented standard for Markdown, and get, say, all my friends to use it and provide feedback; that wouldn't make it popular enough to be included in a browser.
  - mrottenkolber 10y ago
    CommonMark has not published a formal grammar.
- gsnedders 10y ago
  > For example, work on HTML5 can be traced back as far as 2004, meaning that from inception to release, development took about a decade. For some more specific reference points: Web Applications 1.0, as it was then, first defined the parser some time between February 2006. It first shipped in a browser (as the normal HTML parser) in Chrome 7 in October 2010. The parser was in the latest release of every major browser with IE10 shipping in September 2012. In a sense, therefore, when it came to parsing it took under seven years.
- flukus 10y ago
  > Browsers implement well-defined web standards, which Markdown unfortunately isn't. What? All of today's browsers can trace life back to before standards existed and they are constantly adding experimental, non-standard functionality.
- deleted 10y ago
  [deleted]

dom0 10y ago

Because there are dozens of more or less incompatible markdown dialects.

verandaguy 10y ago

Browsers implement well-defined web standards, which Markdown unfortunately isn't. The original author, John Gruber (of daringfireball.net), hasn't been too supportive of having a single, fixed Markdown standard, and this has resulted in spinoffs with various syntaxes and features: - GitHub-flavoured Markdown - CommonMark - etc... On top of that, there isn't even some meta-standard which would allow hashbang-style preambles/doctype declarations to determine which version of Markdown is being served. So, between the fact that there's no fixed de-facto standard and no de jure standard syntax or feature set recognized by any of the major standards bodies (IETF being one of these), it would be impractical for browser vendors to implement support for Markdown. Finally, the standards that browsers implement take time both while being defined, as well as while being implemented; these are things that will be seen by billions of people worldwide, and there's extremely little room for error, so revisions are always necessary at every stage in development. For example, work on HTML5 can be traced back as far as 2004, meaning that from inception to release, development took about a decade.

Ajedi32 10y ago
Couldn't they just adopt CommonMark? That flavor already has a complete spec and test suite, and is specifically designed to be as compatible with existing implementations as possible. I believe the only thing really missing is for more of the community to start rallying around the standard.
- verandaguy 10y ago
  Community engagement's a big part of it, though. I can define my own, extremely thorough and well-documented standard for Markdown, and get, say, all my friends to use it and provide feedback; that wouldn't make it popular enough to be included in a browser.
- mrottenkolber 10y ago
  CommonMark has not published a formal grammar.
gsnedders 10y ago
> For example, work on HTML5 can be traced back as far as 2004, meaning that from inception to release, development took about a decade. For some more specific reference points: Web Applications 1.0, as it was then, first defined the parser some time between February 2006. It first shipped in a browser (as the normal HTML parser) in Chrome 7 in October 2010. The parser was in the latest release of every major browser with IE10 shipping in September 2012. In a sense, therefore, when it came to parsing it took under seven years.
flukus 10y ago
> Browsers implement well-defined web standards, which Markdown unfortunately isn't. What? All of today's browsers can trace life back to before standards existed and they are constantly adding experimental, non-standard functionality.
deleted 10y ago
[deleted]