Not really. HTML has a formal standard and definition that covers how to properly handle most corner cases that can arise when displaying it. Markdown has no overarching formal standard and exists in multiple dialects which are not always compatible with each other.
On the gripping hand, HTML involves more keystrokes (and technically speaking you need to include a bit of boilerplate in the file for it to be proper HTML). So it depends on whether you’re willing to do a bit more typing to make sure that no one can possibly confuse your italics with boldface.
Tags interfere with human readability. Open any markdown file with a text editor in plain text and you can basically read the whole thing as it was intended to be read, with possibly the exception of tables.
There’s a time and a place for different things, but I like markdown for human readable source text. HTML might be standardized enough that you can do a lot more with it, but the source file itself generally isn’t as readable.
Not really. HTML has a formal standard and definition that covers how to properly handle most corner cases that can arise when displaying it. Markdown has no overarching formal standard and exists in multiple dialects which are not always compatible with each other.
On the gripping hand, HTML involves more keystrokes (and technically speaking you need to include a bit of boilerplate in the file for it to be proper HTML). So it depends on whether you’re willing to do a bit more typing to make sure that no one can possibly confuse your italics with boldface.
Tags interfere with human readability. Open any markdown file with a text editor in plain text and you can basically read the whole thing as it was intended to be read, with possibly the exception of tables.
There’s a time and a place for different things, but I like markdown for human readable source text. HTML might be standardized enough that you can do a lot more with it, but the source file itself generally isn’t as readable.