Go is not difficult to maintain at large scale, I mean take Kubernetes for example, it's "trivial" to understand and modified even though it's in the millions loc.
replyGo’s much faster compile times are a big advantage over Rust.
replyRust is unstable and slow to compile. I think these two features make it bad for LLMs and everything else.
replyWhy do you say it's unstable?
replyTake async for example. You have to choose some third-party async runtime which may or may not work with other runtimes, libraries, platforms, etc.
replyWith Go, async code written in Go 1.0 compiles and runs the same in Go 1.26, and there is no fragmentation or necessity to reach for third party components.
It is literally being changed constantly. They chose to add it to the Linux kernel but they have to build the features they need into the language as they go. It's not backward compatible like C and C++ either. Sure, there are a couple of versions you could try to pin to in Rust, but then all your libraries need to be pinned to the same version (to be fair, this last part is an assumption).
replyWhere is Rust unstable?
replyRust is harder for the bot to get "wrong" in the sense of running-but-does-the-wrong-thing, but it's far less stable than Go and LLMs frequently output Rust that straight up doesn't compile.
replyLLMs outputting code that doesn't compile is the failure mode you want. Outputting wrong code that compiles is far worse.
replySetting aside the problems of wrong but compiling code. Wrong and non-compiling code is also much easier to deal with. For training an LLM, you have an objective fitness function to detect compilation errors.
For using an LLM, you can embed the LLM itself in a larger system that checks it's output and either re-rolls on errors, or invokes something to fix the errors.
If you use the stable version of Rust, it's stable. There's a very strong commitment from the Rust folks on that specific point.
replyThe only thing I see is the LLM not being aware of new features, so I have to specify the version rust.
reply