> I haven't met anyone who knows Typst even exists.
It was released in 2023 and became polished enough to use like last year. Yeah, adoption takes time but the technology is significantly better.
> The problem is also momentum. Do you rewrite 30 years' of CTAN contributions, internal templates/styles and the toolchain off and start again or not?
With latex you have to rely on third party. With typst you can write it yourself (or with an agent), like writing functions is not painful in typst.
> It's cool sure, powerful also... but when anybody has access to both vector-based editor and raster-based editor ... but also tools that incorporate them, e.g. rich text editors ... but also entire toolchain going from compilers to libraries all the way to Web based notebook with their editors and running environment that can then output printable artifacts, I don't think there has to be "the" way. They might be a more popular way within a certain zeitgeist but... does one project has to "replace" another one?
cool, why do you think people use tikz? And like generating images programmatically from text is impossibly more powerful than using vector editors.
The problem with markdown is that it's not extensible and that there is no spec. Essentially all READMEs would be better off using typst, they would make for better READMEs.
Almost exactly a year ago, I made the switch from generating LaTeX from markdown using pandoc to typst. Best decision I have ever made. I can actually write my own macros (both LaTeX and pandoc were a pain in the ass).
The ecosystem is not quite a mature as latex, however I can implement the things I need myself.
Twitter: https://twitter.com/adamnemecek1
GitHub: https://github.com/adamnemecek