3 ms·
I think the author is missing a fairly major point, that Markdown was intended to be a way to process text written the way people already wrote it. ASCII is ab
by Gordonjcp 4y ago
I think the author is missing a fairly major point, that Markdown was intended to be a way to process text written the way people already wrote it.
ASCII is absolutely the best way to write documents, if you're working in a primarily ASCII environment. Crabbit old bastards like me who remember the dialup BBS days consider Markdown-like text to be standard - underline things with a row of hyphens, mark a heading by underlining with # symbols or = symbols depending on how "strong" you want the heading to be, emphasis words with *asterisks like this* and italicise with /slashes like this/ (okay they got that one a bit wrong but still the point stands). Make a bulleted list by indenting a bit and putting a * at the start of the line, and so on.
Before Markdown-the-specification and set of libraries to transform text to HTML existed, there were already a wealth of documents in somewhat Markdown-like syntax. Being able to transform them into something that "kids these days" with their high-resolution 800x600 pixel bitmap displays can view in a cool font came long after.
- jrib 4y agoI wish the slashes for italic had made it into what is currently Markdown. /italics/ and *bold* feel much more natural to me than having to remember whether a single asterisk (text) or double asterisk (*text*) corresponds to italics or bold.
- pessimizer 4y agoYou can escape asterisks on HN with \.
- Gordonjcp 4y agoThere's nothing stopping you forking a project like Github did and making a Jrib-Flavoured-Markdown parser. I'd use it, just to get the italics and bold right.