I have been keeping markdown notes for 10 years and have never had issues. I suspect the last 10 years is a decent predictor for the next 10 years, given the existence of github as a fairly strong touchstone.
I have lately been rendering everything as HTML using hugo + mathjax.
> If you are strictly going to stick with Hugo forever, then that's fine. But how many of us can guarantee that we want to keep using the same tool to render our Markdown for ever? I certainly can't!
The problem I have is that I don't want to lock myself into one single Markdown renderer like Hugo or whatever it uses internally. I'd like the flexibility to change tools later without worrying that the new tool may break the rendered output.
Like I said, not even something as basic as nested lists are rendered the same way by all tools. What is rendered as nested list by one tool is rendered as a broken list with unexpected code blocks interspersed between them.
A single spec consistently implemented by all tools could fix these issues. Sadly such a spec does not exist in the Markdown world. That's really why I was looking for something like C89 of the Markdown world.
That makes sense. I did ninja edit, probably as you were commenting, about how I've been using 10 years and only lately like hugo, but have no issues regardless.
Github has been fairly stable as a markdown center of gravity. That works fine for me too.
For me, I don't find the need for 100 year compatibility to be a stopping point. 10-20 years is far away enough for me, otherwise the perfect becomes the enemy of good.
I have lately been rendering everything as HTML using hugo + mathjax.