> Because web browsers are supposed to render HTML, not markdown. Ok but they could also render Markdown. > When presented with a file full of markdown, how s

> Because web browsers are supposed to render HTML, not markdown. Ok but they could also render Markdown. > When presented with a file full of markdown, how should the browser present it? Render it on the screen. > Black text on white? Opposite? Something else? ... The browser can pick a sensible default, just like it does with HTML. How do you think GitHub manages to render Markdown? It picks a sensible default. > That's not considering the dozens of flavors of markdown Send the flavour in the MIME type. (Not sure we have MIME types for different flavours, but we could do that.)