I'm surprised nobody has yet mentioned how pleasant it is to create coffee stains using Typst, and if only LaTeX wasn't the de-facto standard in academia and stain-related journals, they would have already switched to it.
Of course, you can create coffee stains in HTML as well, but it's not something you can do in Markdown.
I know it was probably said just as a joke, but are you really writing papers using Rust? I don’ t use Rust, BUT if you’ve got a better way to write symbol heavy type theory and/or logic than having to make PNG’s and put them in as images in a word processor I would love to hear about it.
That package still has the core limitation of Typst: images can only be placed top-middle-bottom and left-centre-right. Typst still has yet to support arbitrarily placed images.
You mean absolutely positioning it? You can do that with the place function and displacing it with dx/dy from the origin (https://typst.app/docs/reference/layout/place). Example: #place(top + left, dy: 2cm, dx: 4cm, image("image.png"))
That seems usable for manual layout, but it looks painful to use to place images without knowing exactly where they might end up on a page. I reuse my LaTeX code to make volumes of books, and I never touch the code. It's fire and forget for me, which this does not seem to solve.
Parameterize! That's a new word I didn't know. It adequately describes how I typeset my books, and I must not be alone. The ability to tell LaTeX to drop a picture around here, to the best of its ability, with the possibility of moving it down a paragraph or two if it doesn't fit is vital for me.
I think that's a missing feature of Typst yes, to have figures be either "here" or "top next page" automatically, with that priority. It can't do that.
The confusing part was that this has nothing to do with the images of this coffee stain package, because they are foreground/background and can be placed freely on the page (any corner or any custom offset from any corner; i.e from top left corner you can use page coordinates).
The coffee stains overlay/underlay text, so no layout problems at all.
But the dx/dy arguments also take percentages besides absolut lengths. I still don't get what the the other poster means by that fundamental limitation. I think they're confused about absolute positioning of background images vs floating figures. But typst has the analog setting of `[htbp]`, so the same "fire and forget" workflow is possible.
The compiler is open-source and can be run locally. You need an account if you want to use their web editor, which is nice (it shows error messages where they occur along with an explanation and link to docs, and also shows a real-time updated preview).
As for Latex vs Typst, as a language Typst is much better, compiles very quickly, and has sane error messages. However, Typst still has a few rough edges, and can't do everything you can with Latex + packages (yet).
I've been using Typst for most of my documents for a few months and I've been generally happy with it.
I have never really used the web thing personally. I always use the command line version, and it works perfectly fine and it's FOSS.
I find the syntax to Typst to be generally better than LaTeX. I don't like its equations as much, but Typst has one huge advantage that makes it easier to forgive its faults: it compiles several orders of magnitude faster than LaTeX. This might not sound like much but it honestly sort of changes how you even think about problems. I keep Neovim open on the left, run `typst watch` in the background, and Evince on the right, and my updates show up immediately upon saving.
Also, adding plugins and libraries is trivial. All you have to do is declare it at the top of the file and it will automatically fetch it, which is considerably easier than LaTeX.
I don't like the default font it ships with, but it's easy enough to add a Latin Modern font and get something that looks like LaTeX.
Before Typst, I had typically been using Pandoc with Markdown to write my documents, and that served me well for quite awhile, but it had the disadvantage of being extremely slow to compile. A slide deck that I gave last year [1] would take a bit more than a minute to compile. This became an issue because I had to make a few small last-minute changes and having to wait an entire minute to view them actually made it so I was really pushing against the wire.
If I had done my slides in Typst, they would have compiled in about 40 milliseconds, they wouldn't have looked any worse, and I'd have a syntax not dissimilar to Markdown. I'm pretty much a convert at this point.
There is a very prominent web site that offers a hosted version without much clarity about the fact that you can run it yourself. The hosted version offers collaborative editing similar to what Overleaf provides which is incredibly useful.
Typst is an application you can use on your local machine without any signup. The compiler is hosted on GitHub. The Typst web app (the online editor at typst.app) is closed source and offered as a paid with cloud storage, collaboration, autocomplete, etc...
Everybody knows that coffee stains are the only surefire way to tell whether a paper has been read or just printed out and ignored. A colleague in uni (way back in early 00s) would add these to her documents every once in a while to give them the "has been read" stamp of approval.
Maybe I'm just missing the joke, but it feels worth pointing out that almost all of the logos on that page are clearly inspired by the ensō circle from Zen art.
This looks nice, but it is just placing some pre-defined vector files. I wonder if it could be possible to procedurally generate realistic coffee stains.
Love this. My resume has been in LaTeX for over 20 years now.
Underappreciated IMHO. You can version control it, no dealing with wild Word shenanigans. Totally deterministic. Just find a style, insert your bullets and you have a nice sharable PDF.
Nowadays you can even have your preferred LLM do the conversion for you. LaTeX is finicky and I've had it fix warnings in mine that I couldn't be bothered to.
Good stuff, highly recommend a LaTeX resume, whether or not you drink coffee.
Any particular template you'd recommend?
My resume is LaTeX too but I'm not 100% happy with it (about 98% happy and much happier than with anything else however).
You need to go all-in on tea and make your own mark. Get a fancy Chinese teapot with holes in the spout to use loose leaf tea, and start getting snobby about traditional vs modern techniques of Pu'er tea, and you'll get your own brand of respect!
This is wonderful to see. I was a student and then entered into the tech industry in the mid 90's and at that time the Internet had fun whimsical things like this almost weekly.
Obviously this was whimsical when it came out. However...we were creating synthetic data for training and testing OCR in multiple scripts. We would take a web page in some language with a non-Roman script, and reproduce it as multiple PDFs using different fonts. We also added various kinds of blurring, using ImageMagick and---of course---this very coffee stains program!
And even then, when people have good intentions they don't anyways know about edge cases. Please give things a licence in addition to placing it in public domain, because in some countries (like Australia) you can't release your rights that way.
Coffee stains should look like water color paints. The fluid deposits pigment more at dry boundaries as evaporation and absorption approach equilibrium.
There’s an old story about that. Possibly apocryphal, but here goes:
IBM mainframes used to come with documentation in ring binders. Some pages might indeed be marked “This page intentionally blank”. And they would from time to time send out update packages to their customers, with instructions to replace pages so-and-so with the included replacements. On the replacement pages, text that had been altered would be marked with a change bar in the margin.
Lo and behold, one day an update package was received, replacing one completely blank page with one bearing the text “This page intentionally blank”. Complete with a change bar in the margin.
Of course, you can create coffee stains in HTML as well, but it's not something you can do in Markdown.
[0]: https://coffeescript.org/
https://typst.app/universe/package/fleck/
they end up exactly at the specified location?
The coffee stains overlay/underlay text, so no layout problems at all.
Blood. That's blood.
As for Latex vs Typst, as a language Typst is much better, compiles very quickly, and has sane error messages. However, Typst still has a few rough edges, and can't do everything you can with Latex + packages (yet).
I've been using Typst for most of my documents for a few months and I've been generally happy with it.
I find the syntax to Typst to be generally better than LaTeX. I don't like its equations as much, but Typst has one huge advantage that makes it easier to forgive its faults: it compiles several orders of magnitude faster than LaTeX. This might not sound like much but it honestly sort of changes how you even think about problems. I keep Neovim open on the left, run `typst watch` in the background, and Evince on the right, and my updates show up immediately upon saving.
Also, adding plugins and libraries is trivial. All you have to do is declare it at the top of the file and it will automatically fetch it, which is considerably easier than LaTeX.
I don't like the default font it ships with, but it's easy enough to add a Latin Modern font and get something that looks like LaTeX.
Before Typst, I had typically been using Pandoc with Markdown to write my documents, and that served me well for quite awhile, but it had the disadvantage of being extremely slow to compile. A slide deck that I gave last year [1] would take a bit more than a minute to compile. This became an issue because I had to make a few small last-minute changes and having to wait an entire minute to view them actually made it so I was really pushing against the wire.
If I had done my slides in Typst, they would have compiled in about 40 milliseconds, they wouldn't have looked any worse, and I'd have a syntax not dissimilar to Markdown. I'm pretty much a convert at this point.
[1] https://git.sr.ht/~tombert/lambda_days_2025
There is a very prominent web site that offers a hosted version without much clarity about the fact that you can run it yourself. The hosted version offers collaborative editing similar to what Overleaf provides which is incredibly useful.
See https://github.com/typst/typst for the CLI version
There is a page with pre-compiled binaries as well and on Macs, you can install using homebrew.
What the core lacks is the web service that offers e.g. collaborative editing.
Or install it using vscode's extensions, or install it for neovim using mason. That's a few commonly used distribution paths.
https://badspot.us/Brown-Ring-of-Quality.html
Go for it!
Previously: https://news.ycombinator.com/from?site=hanno-rein.de and https://news.ycombinator.com/item?id=39316193
This also reminds me of https://news.ycombinator.com/item?id=30024165
https://youtu.be/r8nTifCIr0c
Underappreciated IMHO. You can version control it, no dealing with wild Word shenanigans. Totally deterministic. Just find a style, insert your bullets and you have a nice sharable PDF.
Nowadays you can even have your preferred LLM do the conversion for you. LaTeX is finicky and I've had it fix warnings in mine that I couldn't be bothered to.
Good stuff, highly recommend a LaTeX resume, whether or not you drink coffee.
Diet soda sometimes works, but often isn't provided as easily.
Good times.
* tea strains
* bread crumbles (squashed among paper leaves)
* tomato sauce drops
* hair
> A lot of time can be saved by printing [extra stuff] directly on the page rather than adding them manually!
Unfortunately the challenge was a bit too hard and went unsolved during the competition.
I like the author's note about the license: "As we do not believe in imaginary property, this package belongs to the public domain."
I think it's much more common to see a Creative Commons license on this sort of thing.
IBM mainframes used to come with documentation in ring binders. Some pages might indeed be marked “This page intentionally blank”. And they would from time to time send out update packages to their customers, with instructions to replace pages so-and-so with the included replacements. On the replacement pages, text that had been altered would be marked with a change bar in the margin.
Lo and behold, one day an update package was received, replacing one completely blank page with one bearing the text “This page intentionally blank”. Complete with a change bar in the margin.
https://github.com/mscroggs/realhats