> A 500KLOC codebase in Java would usually be half that size in Rust Ok, so you barely know either Java or Rust. > If your argument is that large codebases ma

> A 500KLOC codebase in Java would usually be half that size in Rust Ok, so you barely know either Java or Rust. > If your argument is that large codebases makes life harder for agents, you should go with a less verbose language. You mean, like Rust??? But no, that's not my argument. Agents have a hard time keeping up the architecture in large software (and the differences between verbose languages like Java, Go, Rust, and C++ vs less verbose ones like Python and JS don't make much of a difference). So they either make a mess or they do the simple thing, and the simple thing in low-level languages is often slow. > But it wouldn't be worse on the slop that humans created on every moderately-sized Java project I've worked on. Yeah, I don't think you've actually tried it. > I've never seen an agent optimizing for Java where necessary (e.g. using object pools to avoid GC churn). Java is not magic. Object pools are far less efficient than Java's GCs, but while state-of-the-art compiler and memory management technology is certainly not magic, I suggest you learn more about these things if you want to make informed decisions.