I would really like to see a comparison of all these tools/markup languages:<p>- MyST<p>- Pandoc<p>- Quarkdown<p>- Quarto<p>- Typst<p>Quarto and pandoc both use Pandoc Markdown (and so does <a href="https://www.zettlr.com/" rel="nofollow">https://www.zettlr.com/</a>). But Quarkdown and Typst offer programmable markup languages like LaTeX (or HTML + Javascript). It seems the winner for the title official LaTeX successor is still not decided.
You mean like this? <a href="https://github.com/iamgio/quarkdown#comparison" rel="nofollow">https://github.com/iamgio/quarkdown#comparison</a>
Consider djot for the comparison list too.<p>It seems like a well designed and thorough superset of markdown.<p><a href="https://djot.net/" rel="nofollow">https://djot.net/</a>
I am currently enjoying WYSIWYG with GNU TeXmacs for long-form or scientific text editing. Both, the concept and the tool, are amazingly capable and a breath of fresh air after all the LaTex, Markdown, Org s …
Thanks. The list also includes <a href="https://mdxjs.com/" rel="nofollow">https://mdxjs.com/</a>, which I have never heard of.
I've produced a staggering variety of documents with Typst. Books, booklets, slides, cards, documentation, everything. In most cases I only need a minimum of custom styles and behaviors at the top, and very occasionally a whole styling module. Blows the rest of these tools out of the water full stop.
I don’t think adding things to markdown is a good way to go. Markdown is just a poor language, period. Alternatives like Asciidoc make much more sense IMHO.
On a quick read of the docs I'm a bit worried Quarkdown doesn't have the right evaluation model for the job. Text layout typically iterates to a fixed point, because adjusting the layout of one part of the document can throw out layout at another part, require another layout pass and so on. Typst has the concept of context[1] for this. I didn't see anything in Quarkdown that seemed similar, though perhaps I missed it.<p>I switched from pandoc / md / LaTex to Typst for my book[2], and have been very happy with it. Programming in a modern language is nice, and Typst is much faster than pandoc + LaTex.<p>[1]: <a href="https://typst.app/docs/reference/context/" rel="nofollow">https://typst.app/docs/reference/context/</a><p>[2]: <a href="https://functionalprogrammingstrategies.com/" rel="nofollow">https://functionalprogrammingstrategies.com/</a>
It's nice in that it extends markdown rather than reinventing a different syntax.<p>But the point of markdown, is to simply, markdown. Everything beyond that is deemed superfluous and cumbersome as it would defeat the point. Just write things down.<p>It's the right balance between plain text and latex and the rest.
Nice! But in the Comparison should be MyST - <a href="https://mystmd.org/" rel="nofollow">https://mystmd.org/</a> This is the new markdown standard to be….
I was looking for something like this, but would love if it had CV formatted doc. I just want something easy to update, but easier to version control Vs docx.
The nice thing is that with LLMs using markdown we are getting a nice ecosystem for a universal method for communicating textual information. The negative is that Markdown is starting to look like the <a href="https://xkcd.com/927/" rel="nofollow">https://xkcd.com/927/</a> cartoon.
The silly part is having n+1 Markdown standards that all end up rendering as HTML anyway. Personally if it's a plain text file sure, basic Markdown is fine, beyond that just give me some kind of rich text editor that stores as HTML and let me do whatever and not have to hand format a Markdown table.
demos look super clean!<p>I try to support multiple formats on my app: typst, mdx, marp, reveal, latex.<p>i think it should be possible to add support for quark down too<p><a href="https://sublimated.com/docs/typst" rel="nofollow">https://sublimated.com/docs/typst</a>
<a href="https://sublimated.com/docs/typst/demo/article.typ" rel="nofollow">https://sublimated.com/docs/typst/demo/article.typ</a>
how is it for converting streaming api responses from LLM's?