4 ms·
For me, notably absent from the release changelog and accompanying YouTube video they were excited to trumpet in the blog back in July, and the claim (still) th
by slowpoke-tail 1mo ago
For me, notably absent from the release changelog and accompanying YouTube video they were excited to trumpet in the blog back in July, and the claim (still) this took 11 days. It's August 20th.
- sionisrecur 1mo agoYes, I'm fine with the AI rewrite, just don't claim it was done in 11 days when it actually took ~50.
- rwz 1mo agoThe rewrite part of get to functionally equivalent to the existing zig version in rust did in fact take 11 days based on the available data. When that was done, they spend some time on a ton of new features and hardening and bugfixing that the Rust rewrite enabled. This took additional time.
- dolmen 1mo agoAt the end of the 11 days, reviews raised much use of unsafe blocks. I guess this is much reduced by now, and the effort required on that front should not be rejected from being part of the migration.
- theshrike79 1mo agoIt _worked_ after the 11 day migration. Getting rid of unsafe blocks (Which were AFAIK partly a Zig inflicted thing) was just polish.
- voiper1 1mo agoWeird there's no information about that here. But if they went down in cpu usage and memory usage, removed a memory leak, and are MORE compliant with nodejs... it sounds like a MASSIVE success?