Remix.run Logo
jimmar 13 hours ago

Markdown is the minimum viable product. It’s easy to learn and still readable if not rendered in an alternate format. It’s great.

For making PDFs, I’ve recently moved from AsciiDoc to Typst. I couldn’t find a good way to get AsciiDoc to make accessible PDFs, and I found myself struggling to control the output. Typst solves all of AsciiDoc’s problems for me.

But in the end, no markup language will make you write better. It’s kind of like saying that ballpoint pens are limiting your writing, so you should switch to mechanical pencils.

hobofan 2 hours ago | parent | next [-]

Yes, the author conflates two different use-cases.

Markdown is the answer for "how do we enable people that don't want to invest a lot of time into producing content that's somewhat better than plain text?".

It's not trying to solve the problem of "how do we enable people that are willing to invest time into learning to produce the best possible and most structured content possible?" and I doubt that there will be language that will serve both of those use-cases very well.

swiftcoder 12 minutes ago | parent [-]

One downside here is that as more and more tools focus on the first use-case, people start using those tools by default when they actually fall into the second use-case. And there's often a pretty high barrier to switching once you've produced a lot of content, so a bunch of projects are using the wrong one long-term.

eproxus an hour ago | parent | prev | next [-]

Djot is another interesting alternative that tries to make Markdown more parsable and coherent: https://github.com/jgm/djot#rationale

undeveloper 12 hours ago | parent | prev [-]

typst looks interesting -- but how are you writing it? from what I looked at, it looks like theres an official web editor and a vscode plugin with limited support. this feels pretty limited, as someone who came in expecting something like obsidian.

MillironX 11 hours ago | parent | next [-]

I've started experimenting with Typst for a few documents, and here's my stack:

- Zed editor with Typst plugin

- Tinymist LSP settings turned on to render on save in Zed, see https://code.millironx.com/millironx/nix-dotfiles/src/commit...

- Okular open to the output document. Okular refreshes the document when changed on disk.

It's not as polished as say, LaTeX Workshop in VSCode, but it gets the job done.

TRiG_Ireland 12 hours ago | parent | prev | next [-]

I'm not aware of any limitations in the Tinymist plugin.

And you can just write it in the plain text editor of your choice, and keep an eye on the PDF with typst watch.

addaon 10 hours ago | parent [-]

> I'm not aware of any limitations in the Tinymist plugin.

I looked into this a while ago, and couldn't find a workflow I could live with. Have things improved? What's the workflow like for working on an image in, say, OmniGraffle to include in the document? Does text search in embedded PDFs work these days? LinkBack so I can edit the images easily inline?

tcfhgj 2 hours ago | parent | prev [-]

you can just install the typst compiler yourself and let it run in the cli

    typst watch file.typ // compiles automatically on file changes