Laurenz

[Laurenz @laurmaedje]

@avaitopiper @typstapp https://t.co/MaTQm35xH3

[Laurenz @laurmaedje]

@tonofcrates I do think though that this is one of the upsides of Typst being a company: We can make OSS maintainance part of a paid job. It's already starting with some pieces (package ecosystem & bibliography management), but we definitely want to expand this to the compiler in the future.

[Laurenz @laurmaedje]

@tonofcrates I think that the contributor experience is important and for that reason I always tried to review things quickly. But lately I had to scale that back a bit to be able to make progress on the foundations of the language. There just isn't always enough time and mindspace for both.

[Laurenz @laurmaedje]

@MyJimmyTingles @typstapp Yep, it works just the same locally. The compiler will download the packages on demand.

[Laurenz @laurmaedje]

@Nico_Weio @typstapp I think you have the wrong link. It should be: https://t.co/C3ggBcUZHk

[Laurenz @laurmaedje]

@ayoubElMhamdi @typstapp Typst shouldn't create any temporary PDFs by itself. Are you using the third-party Typst LSP extension? It will do this, but you can also disable it.

[Typst @typstapp]

We are a real language now!

[Laurenz @laurmaedje]

@aspiwack @typstapp Just one small note (as a Typst dev): set does not just assign/preapply arguments, it also affects all content that was created *outside* of its scope, but put into its scope, as demonstrated by the example below. This makes styling composable.

[Typst @typstapp]

In the previous thesis you learned why Typst is fast, in Laurenz' thesis you can now look behind the scenes and see how it was designed: https://t.co/e8dlS5NDuI