Ill preface my comment with saying: this might not be the best solution give the goal of your project to iteratively loop through and improve on the tests each round, and using deps would make that process longer/more complicated having to work potentially with another project.
.....however.....
mago, a static analyzer for php is written in rust and might be useful for gaining some "free" performance uplift: https://github.com/carthage-software/mago. iirc it splits out a far bit of its internals so they can be used by other projects (citation needed)
Maybe the takeaway is that 20% is about all the LLM can muster.
> Maybe the takeaway is that 20% is about all the LLM can muster At this point there's a long list of projects that have used LLMs to rewrite a system in Rust including: - Bun (https://github.com/oven-sh/bun/pull/30412) - Valkey (https://github.com/ianm199/valdr) - Git (https://github.com/gitbutlerapp/grit) - Postgres (https://github.com/malisper/pgrust) With the exception of Bun, these projects were done pre-fable t…
I'm not sure about the other three, but Bun's rewrite from Zig to Rust was a bit of a joke. `unsafe`s in the thousands, a quarter-million lines of diff, and merged inside a week with no significant public discourse (at least, not much that was responded to by the author).
Does anyone know why we write code anymore? Why not pass through to an llm that generates the page on the fly (ssr)? Is it cost ?
Yes: cost, speed, and reliability. But all of those things are improving at shocking speeds, so I think we’re on a path where code is losing value quickly.
Yeah, I agree. It will be like serverless but for code : codeless.
Is it astonishing you got to 17% with some vibe code? Sure. But most of the stuff I’ve vibe coded this year has been astonishing by 2025’s standards. If you got 100% I’d be genuinely blown away.
> Maybe the takeaway is that 20% is about all the LLM can muster At this point there's a long list of projects that have used LLMs to rewrite a system in Rust including: - Bun (https://github.com/oven-sh/bun/pull/30412) - Valkey (https://github.com/ianm199/valdr) - Git (https://github.com/gitbutlerapp/grit) - Postgres (https://github.com/malisper/pgrust) With the exception of Bun, these projects were done pre-fable t…
I'm not sure about the other three, but Bun's rewrite from Zig to Rust was a bit of a joke. `unsafe`s in the thousands, a quarter-million lines of diff, and merged inside a week with no significant public discourse (at least, not much that was responded to by the author).
Still waiting on that blog post from Jarred that will supposedly answer all the questions and concerns about the rust port.
Yes: cost, speed, and reliability. But all of those things are improving at shocking speeds, so I think we’re on a path where code is losing value quickly.
Yeah, I agree. It will be like serverless but for code : codeless. It’s a disconcerting future.
Is it astonishing you got to 17% with some vibe code? Sure. But most of the stuff I’ve vibe coded this year has been astonishing by 2025’s standards. If you got 100% I’d be genuinely blown away.
Does anyone know why we write code anymore? Why not pass through to an llm that generates the page on the fly (ssr)? Is it cost ?