One of the thorniest conversions was the session.ts file, which was over 30,000 lines of TypeScript that touched all aspects of the runtime.

- there are now ridiculous vibe coded localisation in VS2026

- task manager started to not report cpu usage correctly recently (the number becomes stalled)

- file explorer display the "loading" icon infinitely on some directories

- and many other things!

Though it's the same extension that can't keep its session timestamps straight, randomly hides sessions I was just in (then suddenly remembers them after going in and out of a session), and completely shits itself visually when using OpenAI's models, so maybe it really is the latter.

The +400k new lines were probably code comments the agents added to everything

Does this impresses/surprises anyone? Two folds: 1) I believe the most optimized JavaScript code could near the performance of this phase 1 port without optimizations. I would have gone with that first, many would think that would not be as cost efficient but: 2) optimizing the rust code will require 10x the effort of the 1 by 1 conversion, just because you now need idiomatic rust code that likely has nothing to do with a plain translation. So defeating the initial gain, there's nothing to do the bottleneck gets just pushed elsewhere

Half of the 832K LoC are mostly tests she answered:

> Yeap, 832,378 lines of production Rust. the +800K number is production only; unit tests are another +469K on top.

https://x.com/acolombiadev/status/2100660224298193081?s=20