4 ms·
For reference, this blog post appears to be by the same person who is the overwhelmingly primary contributor to Typst: See https://github.com/typst/typst/graphs
by zellyn 2y ago
For reference, this blog post appears to be by the same person who is the overwhelmingly primary contributor to Typst: See https://github.com/typst/typst/graphs/contributors https://github.com/typst/typst/graphs/contributors
- leothelion_ 2y agoOne of the two founders of Typst project, in fact https://typst.app/about/ https://typst.app/about/
- reikonomusha 2y agoI found it mildly irksome that the blog post was written almost as if it were a completely unbiased comparison.
- epidemian 2y agoI didn't get that impression at all. The first paragraph includes the sentence: > I want to use this post to explore these differences, to identify the benefits and limitations of both models, and to present my thinking on the future of Typst’s layout engine. Which immediately made me think the author of the post was involved in Typst development.
- sundarurfriend 2y agoI find it mildly irksome that Hacker News readers often assume that blog posts are always written for someone like them - i.e. someone unfamiliar with the author who happened upon the post without context. That used to be the way blogs work, just written for a broad, unknown audience, but these days most blogs are written with a specific audience in mind, often one that knows the author reasonably well. Sometimes the blog is even just a secondary place to have an archive of the post, the main intended place being a post on a close-knit forum. Once you take away the assumption that you're the intended audience, it's much easier to see the article - and the things it says and doesn't explicitly say - in a clearer light.