this post was submitted on 27 May 2025
660 points (99.0% liked)
memes
15345 readers
4102 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would say the general design philosophy. It works pretty much perfectly for what it's supposed to do. But the strong suit of LuaTex is that it can execute pretty much any code you want. So, you could in theory execute a fluid simulation each time you compile your document and insert the result as an image. The Typst Scripting language obviously can't do that because it's locked into the typst sandbox.
My particular use case is that I have some data accessible via an open API and I would love to skip the step where I update the data CSV every day or week. So, not really a breaking feature, but nice to have nonetheless.
At this point a regular Makefile might be in order that can do any data fetching or preprocessing before calling the typst compiler.
Yeah, there's a lot of ways to do this. As I said, it's more of a nice to have feature rather than anything else.