58,444 karma · joined July 23, 2011
Twitter: https://twitter.com/adamnemecek1
GitHub: https://github.com/adamnemecek
For me the larger problems were the lack of types which in practice meant that I was running into the same problems as with bash.
```
let result = try await Subprocess.run(
.name("ls"),
arguments: ["-la"],
output: .string(limit: 4096)
)print(result.standardOutput)`
```
reminds me that macOS could really use something like powershell (I know you can run powershell on macOS) where you pass around structured data, rather than the endless parsing and reparsing. This is mostly a feature of the shell but you do need some language infrastructure to accomplish it.
I hope it does.
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.
cool, why do you think people use tikz? And like generating images programmatically from text is impossibly more powerful than using vector editors.
I predict a future where markdown and latex are largely replaced by typst. And I couldn't be more excited.
It is such a stepup from markdown and latex. Try it today if you are intrigued.
The ecosystem is not quite a mature as latex, however I can implement the things I need myself.
If you are on the fence, do yourself a favor and try it. There is a VS Code extension https://marketplace.visualstudio.com/items?itemName=myriad-d....
For years?