Live data from Hacker News

Quarkdown: A modern Markdown-based typesetting system

github.com

101–110 of 285 posts

Re: Quarkdown: A modern Markdown-based typesetting system

#101
post #83

Markdown, Quardown, Typst, this and that. This looks to LaTeX. All of this became so confusing and un-standardized - I went back to HTML+CSS.

Well basic markdown is super useful to do stuff quickly. Problem is when people started to build systems upon systems upon something that should not be used for more complicated cases. Maybe not a problem because I don't care but I just see how loads of things that someone created to be "just that" someone takes without understanding and builds on top instead of understanding limitations and scope of the initial idea…

I think a good balance for a markdown syntax is something you can write nearly naturally on the fly (very low syntax needed for basic use) but can continue to mark up in more detail when you want to turn something into a complex use case (very high syntax ceiling for the complex cases). HTML+CSS almost gets there except the tags are a bit awkward for simple things like just bolding a word.

Regarding Notepad, keep in mind they dumped an entire separate app (WordPad) by merging the ability to format into Notepad. This kind of mirrors what I was talking about above: one app with a very low floor but a flexibly high ceiling when you want to go there with it rather than two separate apps you need to pick from up front.

Re: Quarkdown: A modern Markdown-based typesetting system

#102
I'm not quite sure who this is for.

Markdown is for keeping things simple.

There's plenty of of "proper" markup languages and full programming languages to actually write code in.

Why do we need a hybrid program like this, which is not as simple as pure markup, and is not as powerful as a proper templating language?

I personally just run markdown -> HTML/CSS -> python templating (Jinja or something) -> PDF/HTML

As a dev, I find this works the best for me. But I also cannot imagine that learning Quarkdown would improve my workflow meaningfully, and I also cannot imagine recommending someone learn such a niche product instead of having them learn HTML/CSS and Python (Jinja if they need fancy). Seems like a comparable amount of effort.

Re: Quarkdown: A modern Markdown-based typesetting system

#104

I'm not quite sure who this is for. Markdown is for keeping things simple. There's plenty of of "proper" markup languages and full programming languages to actually write code in. Why do we need a hybrid program like this, which is not as simple as pure markup, and is not as powerful as a proper templating language? I personally just run markdown -> HTML/CSS -> python templating (Jinja or something) -> PDF/HTML As a…

its for people who want latex but are mad that latex became c++

Re: Quarkdown: A modern Markdown-based typesetting system

#107

I'm not quite sure who this is for. Markdown is for keeping things simple. There's plenty of of "proper" markup languages and full programming languages to actually write code in. Why do we need a hybrid program like this, which is not as simple as pure markup, and is not as powerful as a proper templating language? I personally just run markdown -> HTML/CSS -> python templating (Jinja or something) -> PDF/HTML As a…

its for people who want latex but are mad that latex became c++

LaTeX also has some bizarre defaults like bitmap fonts in a tool designed to allow people to create high quality typeset documents.

Re: Quarkdown: A modern Markdown-based typesetting system

#108

Is the comparison table accurate? - https://github.com/iamgio/quarkdown#comparison Surely LaTeX has full scripting ability even though I wouldn't wish such a punishment on anyone. Surely Quarkdown's gibberish like syntax is not more concise and more readable than Typst? And surely the learning curve is not easier than Typst? I'd say the learning curve is more or less the same as Typst. Surely LaTeX can also produce H…

Pandoc is your friend for this and many other use cases.

Re: Quarkdown: A modern Markdown-based typesetting system

#109

Instead of bolting an engine onto a bicycle to travel long distances, why not just use a motorcycle?

Because muscle-memory is a powerful force, and it's a convenient universal input language.

It's why after years of powershell I still reflexively reach for "ls" not "Get-ChildItem"

( "ls" is aliased by default to Get-ChildItem thankfully! )

Markdown is familiar, easy to use, and very human readable and editable without fear of breaking a compilation step.

Typesetting languages however, TeX, LaTex, postscript or the nightmare of the PDF spec, are not.

If I send someone who doesn't know anything about a document markdown, then there's a good chance they'll be able to make simple edits in their favourite text editor and not screw things up.

If I send someone HTML, they'll likely be able to do simple edits but there's greater risk of breaking elements or styling. Not as bad as with stricter languages, but still significantly more chance than with markdown annotations.

If I send someone some TeX, they'll probably not know what to even do with it, they'll likely get confused and ask for a file format they can use.

Reducing how many different languages we have to master is important, so I think it's great if there's a way to write everything in flavours of markdown.

Write markdown everywhere, and let the backends compile to relevant outputs.

In this instance, it's left perhaps a bit function-heavy so there's still larger "risk", but that's likely something that can be solved through templating.

We have flavours of MD, for github issues, for typesetting, for stackoverflow questions. Slack and Discord have (limited) MD support. We can write blogs in MD through jekyll.

MD is everywhere, it's a convenient universal input language.

Re: Quarkdown: A modern Markdown-based typesetting system

#110

Is the comparison table accurate? - https://github.com/iamgio/quarkdown#comparison Surely LaTeX has full scripting ability even though I wouldn't wish such a punishment on anyone. Surely Quarkdown's gibberish like syntax is not more concise and more readable than Typst? And surely the learning curve is not easier than Typst? I'd say the learning curve is more or less the same as Typst. Surely LaTeX can also produce H…

Pandoc is your friend for this and many other use cases.

Not sure I understand. I never said anything about my use cases. I was checking the accuracy of the comparison table. Did you mean to post that comment here or were you replying to another comment?
Post reply on HN