I mean it was 600,000 lines of Zig prior to the rewrite yea? If we say that a team is ~6 people, that's 100,000 lines each to read through and translate. Assuming 250 working days in a year, that's 400 lines of code you just need to read every day, let alone the Rust you need to be writing (approximately another 400 lines).

Add to that overhead for planning and coordination... I actually think a year for a team might be an underestimate.

Maybe, but it wouldn't have 17000 unsafe clauses 😸

Rust-based JS engine that isn’t just AI generated unsafe everywhere

Tbf only 4% of the code was unsafe after the rewrite, which is much better than the 100% of the Zig code being unsafe. Honestly it's not surprising you'd have such a large amount of unsafe when you translate Zig to Rust. But as I understand it, it's since been refactored to much less than 4%.

unsafe everywhere

Might as well use C at that point.

This should definitely be required follow-up reading, as it puts many of the Bun article's "too good to be true" claims into context.

The fact that the Bun author didn't know that Zig also has LTO really puts the rest of their claims into question.