[jaytaylor]

> The Go to Rust rewrite is interesting - was that driven by performance or more about the ecosystem/tooling for this kind of work?

I'm testing a theory that large-scale (LoC) generated projects in Rust tend to have fewer functional bugs compared to e.g. Go or Java because Rust as a language is a little stricter.

I've not yet formed a full opinion or conclusion, but in general I'm starting to prefer Rust.

Re: generalizing mocks, it sounds interesting but after getting full-fidelity clones of so many multi-billion dollar SaaS offerings, I really like it and am hooked. It pays nice dividends for developing using agentic coders at high scale. In a few more model releases having your own exhaustive DTU could become trivial.

[throwup238]

> The tradeoff is LLMs still struggle to produce good idiomatic Rust consistently so it takes more iteration cycles to get there (good agent tooling helps, linting/checks/etc.) The compile times on those iterations can be brutal sometimes depending on the project size which adds up for sure. The crafty agents can still find ways to satisfy the compiler without actually solving the problem correctly too, so the cheating risk of course doesn't fully go away.

I’ve gone ahead and completely banned ‘unwrap_or_default’ and a bunch of other helpful functions because LLMs just cannot be trusted to use them properly.