I ran into this earlier, the commit history is the one maintainer and Claude pumping out like hundreds of commits 24 hours a day. Aside from the token cost, I’m wondering how this will turn out relative to the official tsgo native push.
Yeah not surprising. But if uses the TS test suite and compares output with tsc byte for byte, then an AI banging its head against the wall for a week should get there eventually.
Comments
I ran into this earlier, the commit history is the one maintainer and Claude pumping out like hundreds of commits 24 hours a day. Aside from the token cost, I’m wondering how this will turn out relative to the official tsgo native push.
Yeah not surprising. But if uses the TS test suite and compares output with tsc byte for byte, then an AI banging its head against the wall for a week should get there eventually.
I think it’s been banging it’s head against the wall for many months now lol
how does it compare to tsx ? https://github.com/privatenumber/tsx
It seems like tsx is a wrapper around tsc for easy compile+run workflow.
tsz seems to be a compiler, a replacement for tsc
Seems like tsx is a wrapper around esbuild, not tsc.
Or https://github.com/samchon/ttsc
This seems cool. Like bun for tsc