Why doesn't CommonMark support strikethrough?Head back
So it seems that good ol' CommonMark doesn't support ~~strikethrough~~ syntax, although major players like GitHub do.
Why is this?
Upon some further - rather short - reading, I've found that the general consensus is that strikethrough is so dated a linguistic tool that they don't find it necessary to include it in the specification.
That's a shame, since editing documents may sometimes require old information be visibly denoted as false or redacted.
Either way, it shouldn't affect us in the longterm, but if it does we'll simply have to switch to a different Markdown spec.
Thanks for reading! // Splashsky