81–90 of 128 posts
Earlier quoted context omitted.
> you focus on all the other programming logic Does that actually happen?
For a model, yeah absolutely. You'll spend virtually 0 tokens on memory safety, which means your token budget gets allocated elsewhere. If you wrote a C codebase you'd need to allocate some portion of your budget towards memory safety.
Earlier quoted context omitted.
For a model, yeah absolutely. You'll spend virtually 0 tokens on memory safety, which means your token budget gets allocated elsewhere. If you wrote a C codebase you'd need to allocate some portion of your budget towards memory safety.
They're not talking about the model, and they're not talking about token budgets.
After bun [1] this is another high-profile project that was ported to Rust by extensively using LLMs. Very curious to see how these rewrites play out. Is the LLM foundation solid enough to build upon and iterate on? Or does this cause projects to become unmaintainable because no person understands the implementation anymore? [1]: https://news.ycombinator.com/item?id=48132488
I'd love to see Asciidoctor vibe-ported to Rust! Have either of these people detailed their methodology & costs?
Had it convert it in this and the stock version, compare the output, fix and repeat.
Earlier quoted context omitted.
For a model, yeah absolutely. You'll spend virtually 0 tokens on memory safety, which means your token budget gets allocated elsewhere. If you wrote a C codebase you'd need to allocate some portion of your budget towards memory safety.
They're not talking about the model, and they're not talking about token budgets.
Interesting how LLMs are possibly putting an end to the era where we were increasingly trading off machine performance for developer productivity.
I love it starts with the usual hand waving, > This is an experimental, work-in-progress port of React Compiler to Rust. ... And then gets merged. So after the craziness to use node on the backend, we are back to using compiled languages to compile Javascript assets and Web resources, just like Java and .NET were doing in the 2000's, however since it is Go and Rust it is cool, not the boring languages grandpas were u…
> And then gets merged.
The initial commit attached to that message was the start of the experiment. Are you reading the first message as if it was the last?
It was merged after 3 months and a huge number of incremental commits. The code that was merged was completely different than the code used to open the experimental WIP PR
Why is it a criticism that they started as a work in progress experiment? That’s how experiments work. It’s normal to push code as a work in progress PR and then add to it over time.
rewrite to rust using AI sound like meme now.
Earlier quoted context omitted.
Java has had native code compilers at very least since Excelsior JET exists, and there is a whole story of commercial offerings, before GraalVM and OpenJ9 come to be, so a moot point in 2026. Likewise, .NET has had NGEN since day one even if with limitations, and after several detours in AOT approaches, NativeAOT is in the package and cross platform, thus also a moot point in 2026. But again, they aren't cool for the…
The point isn't "AOT", the point is an efficient, compiled binary. Acting like Java's AOT story is comparable to a native Rust binary is delusional. And yes, both languages are considered "not cool" since they lean heavily into code structuring that the industry has largely moved past.
It's quite frightening to see how an enormous 120KLOC pull request gets merged at once with very little public discussion or coverage by the devs after just 3 months (which IMO is very little time in relation to the amount of code). There used to be extensive RFCs and series of conference talks long preceding changes this big, e.g. React Fiber. I support wholeheartedly the move to AOT-compiled languages but it looks…
The public contract previously discussed in RFCs and conference talks hasn't changed. Coding language is just an implementation detail.
Earlier quoted context omitted.
The public contract previously discussed in RFCs and conference talks hasn't changed. Coding language is just an implementation detail.
While this is true, the fact that it is Rust provides a much greater level of confidence than if it was Python or something.