Which communication protocol or open standard in software do you wish was more common or used more?

Cyclohexane@lemmy.mlmod to Linux@lemmy.ml – 256 points –

Whether you're really passionate about RPC, MQTT, Matrix or wayland, tell us more about the protocols or open standards you have strong opinions on!

348

You are viewing a single comment

Markdown is terrible as a standard because every parser works differently and when you try to standardize it (CommonMark, etc.), you find out that there are a bajillion edge cases, leading to an extremely bloated specification.

Agreed in principle, but in practice, I find it's rarely a problem.

While editing, we pick an export tool for all editors and stick to it.

Once the document is stable, we export it to HTML or PDF and it'll be stable forever.

Most ppl have settled on Commonmark luckily, including us.

Commonmark leaves some stuff like tables unspecified. That creates the need for another layer like GFM or mistletoe. Standardization is not a strong point for markdown.

I believe commonmark tries to specify a minimum baseline spec, and doesn't try to to expand beyond that. It can be frustrating bc we'd like to see tables, superscripts, spoilers, and other things standardized, but I can see why they'd want to keep things minimal.

Asciidoc is a good example of why everything should be standardized. While markdown has multiple implementations, any document is tied to just one implementation. Asciidoc has just one implementation. But when the standard is ready, you should be able to switch implementations seamlessly.

Have you read the CommonMark specification? It’s very complex for a language that’s supposed to be lightweight.

What's the alternative? We either have everything specified well, or we'll have a million slightly incompatible implementations. I'll take the big specification. At least it's not HTML5.

An alternative would be a language with a simpler syntax. Something like XML, but less verbose.

And then we'll be back to a hundred slightly incompatible versions. You need detailed specifications to avoid that. Why not stick to markdown?

Not if the language is standardized from the start.

Sure it will. It will be a detailed language from the start.