Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gribouille 0.3.0: A Grammar of Graphics for Typst

mickael.canouil.fr

Post reply on HN
Print view View original

11–20 of 101 posts

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#11

Post by zhshnsnnaaka »

utopiah wrote: post #7
adamnemecek wrote: post #4

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.

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 ther…

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.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#12

Post by josephg »

mastermage wrote: post #5
adamnemecek wrote: post #4

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.

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.

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.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#13

Post by TRiG_Ireland »

utopiah wrote: post #7
adamnemecek wrote: post #4

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.

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 ther…

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.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#14

Post by adamnemecek »

tlarkworthy wrote: post #10
adamnemecek wrote: post #6

Earlier quoted context omitted.

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.

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

That is like saying "Ruby is not slow, you can write native extensions in C". No, Markdown is not extensible.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#15

Post by mastermage »

josephg wrote: post #12
mastermage wrote: post #5

Earlier quoted context omitted.

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.

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 oth…

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.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#16

Post by mastermage »

adamnemecek wrote: post #6
mastermage wrote: post #5

Earlier quoted context omitted.

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.

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.

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.

Re: Gribouille 0.3.0: A Grammar of Graphics for Typst

#19

Post by practal »

zhshnsnnaaka wrote: post #11
utopiah wrote: post #7

Earlier quoted context omitted.

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 ther…

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…

I agree with that, that's why I am starting with plain syntax first in https://zero.practal.com, because that is really where all the information/logic lives. But there will also be a presentation layer on top of that, building on the information layer, so with time, I would expect it also to subsume much latex/typst functionality. The "header semantics" I already copied from Markdown.
Post reply on HN