tsonic

I'm out of credits codex pro credits (200 plan) in 4-5 days, and then I switch to claude (another large plan) mostly or just go out more and get Vitamin D. :) I spend most of my time designing and tweaking tests suites, and improving test performance. These commits are almost entirely Codex: https://github.com/tsoniclang/tsonic/commits/main/ - but it's possible only because there's a very large test suite attached to it. All of that is very token intensive. If OpenAI gave me 3x my limits, I'd find ways to eat it up in a week. What do these tokens give me? Well, I think in a week or two, I hope to port the TypeScript-Go compiler back into TypeScript, but compiled to native code. It's probably not particularly useful for most ppl, but it's a hobby project that I've spent the last 7 months on.

For tsonic (https://github.com/tsoniclang/tsonic) which is trying to convert TS to C# and then to native binary via NativeAOT, I took almost the opposite tradeoff from JSIR. JSIR is optimizing for round-trips back to JavaScript source. But since in language to language conversion teh consumer is a backend emitter (C# in my case), instead of preserving source structure perfectly, my IR preserves resolved semantic facts: types, generic substitutions, overload decisions, package/binding resolution, and other lowering-critical decisions. I could be wrong, but I suspect transpilers are easier to build if it's lowering oriented (for specific targets).

I have always used Claude at max thinking levels since it launched. It has never been up to the task. For clarity, the task being this: https://github.com/tsoniclang/tsonic Meanwhile, there are half a dozen other projects (business apps, web apps etc) where it works well.

Yes performance is a big issue, and so is security (or the lack of it). I'm attacking this from another angle: https://github.com/tsoniclang/tsonic Write TypeScript, compile to native code via CLR's NativeAOT. We're almost there, you can see some examples here: https://github.com/tsoniclang/proof-is-in-the-pudding You get everything; real multithreading, stack allocated types, single binary output (x64, ARM64 for Linux/MacOS) etc.