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!
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!
Markdown. Its only in tech-spaces that its preferred, but it should be used everywhere. You can even write full books and academic papers in markdown (maybe with only a few extensions like latex / mathjax).
Instead, in a lot of fields, people are passing around variants of microsoft word documents with weird formatting and no standardization around headings, quotes, and comments.
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.
Man, I’ve written three novels plus assorted shorter form stories in markdown.
There’s a learning curve, but once you get going, it’s so fluid. The problem is that when it comes time to format for release, you have to convert to something else, and not every word processor can handle markdown. It’s extra work, but worth it, imo.
Just set up pandoc and Bob’s your uncle. It’ll convert markdown to anything. You’ll never have to open another word processor.
Nice! Thanks for the tip!
Edit: holy shit, how have I never run across that before? That’s a brilliant program right there.
Pandoc + [your markdown editor of choice] is magic. Some editors even come with Pandoc as a dependency so you can export to more or less anything from the GUI. I think GhostWriter and Zettlr at least (I honestly can’t be sure, I’ve changed editors so often and now I just have some Pandoc conversion scripts in my file manager menu).
For sure, I bet full fledged editors like word don’t even let you import it.
Not correctly, no. Librewriter does a bit better, but still misses some bits
Silly question why can’t you convert markdown to PDF and pass that to publishers?
Because it isn’t doc is docx.
Publishers are pissy about such things. Even self publishing (which is what I do now), the various outlets still have limits to what they will use. Amazon accepts something like three file formats, including their own, and pdf isn’t on the list.
I could just do pdf for directly giving them away to people, but even then, epub is usually a better pick in terms of readability since that’s the standard for actual books since ereaders tend to display it better than pdfs. Most people reading books via files would be using something that can give a better experience with epub vs pdf.
I think Obsidian and Logseq are helping to change this.
Markdown is awesome, I agree! I did not realize you could extend markdown with anything other than html. The html extension is quite nice to do anything that markdown doesn’t support natively, but I wish there was an easier way to extend markdown. Maybe the ones you listed are what I need.
Hedgedoc / hackmd support a good amount of extensions out of the box. I think typora and obsidias do also (but not open source).
Depends on the type of book. Since you need HTML for all non default styles. Therefore, it raises the bar… you need a bit of web dev knowledge which removes the biggest benefit of markdown: simplicity / ease of use.
I frigging love markdown for everything!
My main wishlist for markdown, is a better live collaborative markdown editor. Hedgedoc works, but it’s showing it’s age, and they don’t seem to be getting close to releasing v2.
Etherpad also has a markdown extension, but it doesn’t import / export that well.
It is too basic. I guess something more full-fledged like… typst?
Typst is a typesetting format - an alternative to LaTeX. Asciidoc is more of a competitor to markdown.
Learning that currently.
ReST (restructured text) is a good middle ground. I just wish it had more support outside of the python community. It could use some new/better tooling than Sphinx
I agree 💯