Gribouille 0.3.0: A Grammar of Graphics for Typst

mmcanouil 4 days ago 15 commentsRead Article on mickael.canouil.fr

⚡ Community Insights

Discussion Sentiment

92% Positive

Analyzed from 739 words in the discussion.

Discussion (15 Comments)Read Original on HackerNews

unrealhoang•about 2 hours ago

This is awesome, is there a way to render the graphics/chart in svg so that we can implement something like hover & popup (with data information)?

alhidade•3 minutes ago

Typst supports SVG output natively.

adamnemecek•about 2 hours ago

Typst is the most important open source project of the last 5 years.

I predict a future where markdown and latex are largely replaced by typst. And I couldn't be more excited.

It is such a stepup from markdown and latex. Try it today if you are intrigued.

utopiah•about 1 hour ago

I'm not sure either matter to be honest.

It's cool sure, powerful also... but when anybody has access to both vector-based editor and raster-based editor ... but also tools that incorporate them, e.g. rich text editors ... but also entire toolchain going from compilers to libraries all the way to Web based notebook with their editors and running environment that can then output printable artifacts, I don't think there has to be "the" way. They might be a more popular way within a certain zeitgeist but... does one project has to "replace" another one?

I guess I don't really get the passion some people have for "perfect" rendering. I'm fine with just text, then just readible equations below it, then an OK looking graph. I don't actually care if any of those are pixel perfect. I don't get it.

IMHO in terms of actual knowledge transmission reproducibility and interactivity are way more important. They might not look as good and in fact introduce a TON of complexity but I believe it's better than yet another system that is slightly better looking while being slightly easier, for those people with a specific mindset, to setup and use.

PS: still both Gribouille and Typst are cool projects! Just want to make sure I'm not sounding critical against those efforts.

TRiG_Ireland•39 minutes ago

My primary use for Typst is pretty agendas for my Toastmasters club. https://typst.app/project/rmyyeU17y51rl6ISSqGji9

Typesetting isn't just for science. I like that it looks good; I enjoy the creative step of experimenting with document design; and Typst is just fun to use.

zhshnsnnaaka•about 1 hour ago

I agree but to me it seems humanity has a terminal case of being unable to separate content from presentation. I can see it in this thread with clamoring for Typst in READMEs etc. If READMEs need to be anything they need to be plain bloody text. Markdown is the absolute maximum. Having some “header semantics” defined is fine as that’s universal in a document but let’s keep it simple guys, OK?

Information needs to be plain and clear. Presentation can be fancy. Let’s keep these very, very different things separate. AI will thank you as well.

adamnemecek•about 1 hour ago

> It's cool sure, powerful also... but when anybody has access to both vector-based editor and raster-based editor ... but also tools that incorporate them, e.g. rich text editors ... but also entire toolchain going from compilers to libraries all the way to Web based notebook with their editors and running environment that can then output printable artifacts, I don't think there has to be "the" way. They might be a more popular way within a certain zeitgeist but... does one project has to "replace" another one?

cool, why do you think people use tikz? And like generating images programmatically from text is impossibly more powerful than using vector editors.

mastermage•about 2 hours ago

For Latex I agree thats definitely. Markdown I am unsure as Markdown is not meant for creating documents but to just have a little Richt Text Markup in READMEs and other Text files. Typst needs a compile step and altough that one is fast as hell it is still different from Markdown that renders directly from the file without an intermediary.

josephg•about 1 hour ago

Right; but markdown has expanded beyond that niche. Lots of projects use markdown for other stuff - like mdbook, or for blogs.

I think markdown is a great format for readme files. But for real documentation, the added features of typst are fantastic. Like, being able to write scripts, have figures and custom styling, populate data from JSON files, plugins, typography, numbered sections, footnotes and all sorts of other stuff. Markdown doesn't even support comments properly!

I want typst for blogging, long form articles and documentation. Markdown is great for small stuff. But it doesn't scale.

mastermage•9 minutes ago

Fascinating Ideas I love hearing opinions on this, it enriches me.

I do belive that atleast simple files like for example READMEs will stay and perhaps are better to stay as Markdown. One advantage that has is that while scripting is cool, It make the document not plain text readable which is a tradeoff one can argue.

adamnemecek•about 1 hour ago

The problem with markdown is that it's not extensible and that there is no spec. Essentially all READMEs would be better off using typst, they would make for better READMEs.

mastermage•7 minutes ago

As I said in a previous comment typst especialy with extending via scripting stops being plain text readable. A Markdown file (whatever flavor it may be) is still fundamentaly one vi,nano, Editor, Notepad++ away from being read with all its context included. It is a tradeoff that for READMES I would not want to make.

sbysb•about 1 hour ago

I do not think that is the problem with markdown lol. There are lots of problems with markdown, especially vanilla or the more limited versions of it - but really its super power is that it is readable with a regular text editor (or `cat`) and can be rendered without a compilation step.

Markdown is not competing with latex or typst, it is competing with (and has won against) .txt files

tlarkworthy•about 1 hour ago

Of course it's extensible, you can put HTML in it, and HTML is extensible.