3 ms·
I think most people would prefer there wasn't any ambiguity in the first place. No ambiguity, no 500 different things called XMarkdownY
by Marazan 12y ago
I think most people would prefer there wasn't any ambiguity in the first place.
No ambiguity, no 500 different things called XMarkdownY
- RubyPinch 12y agohas there been any standardization efforts which didn't end up with implementation-specific changes everywhere? admittedly the worst example for such a topic, but, we still don't have a situation where all browsers agree on all renderings, and all of them still don't follow the spec, and in some areas, they don't plan to. I can see html requirement being a pain-point for anyone implementing standard markdown.