I would say the general design philosophy.

[xm34@feddit.org]

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.