undefined

points

by bensyverson18 hours ago |

comments

by dralley17 hours ago|

[-]

I don't think Rust is particularly worse than Go in any of these respects.

- LLMs have clearly been trained on a lot of Rust as well

- Compile times are counterbalanced by strong compiler with excellent error messages, and "cargo check" can catch many issues without a full build.

- If you're willing to accept Go levels of performance from Rust, there's nothing preventing you from using copies and clones rather than borrows, which makes most code dead simple.

- For most major dependency types, there exists a clear "winner" in terms of community adoption, so the fact that it's not in the stdlib is not that problematic.

by bensyverson11 hours ago|

parent|

[-]

I do not think "good error messages" is an even trade for "fast compile times." What happens is the LLM catches the error, then may hit another error, and try again. This leads to more tokens and more latency, and then after all that you have a longer compile time.

With that said, I have not done an extensive amount of agentic development in Rust, so maybe I just don't have the reps to compare fairly.

by nylonstrung8 hours ago|

parent|

[-]

It's less that the error messages are just "good" with Rust, it's that more stuff gets caught at comptime, and many of them can be autoremediated by cargo fix or the compiler itself says exactly what should be changed.

Nothing costs more tokens than an LLM trying to debug errors caused at runtime which doesn't map well to it's "intelligence" compared to what Rust provides

by codexon14 hours ago|

parent|

prev|

[-]

Rust compiles way slower in my experience. This is a major problem because ais need to recompile many times especially when it keeps running into borrow checker problems.

With golang, all borrow checker problems go away. This is a good trade off if your app is not cpu-bound, which most are not. If you need every last drop of performance then rust is a better choice of course.

However, I have run into a few cases of runtime null crashes in go.

by dralley14 hours ago|

parent|

[-]

> and "cargo check" can catch compile issues without a full build.

You only have to compile when you actually want to test the behavior, which tends to be right on the first try more often as a result of the strict compiler.

by joseda-hg17 hours ago|

prev|

[-]

How would you compare it to C#? Stable-ish There's a lot of documentation and plenty of stablished patterns, so LLM can produce it no sweat Everything and the Kitchen Sink Performant, and safeish, even if not null safe

by keithnz9 hours ago|

parent|

[-]

In my experience C# works out pretty good. I wrote a project in Go, it mostly went well, but it had weird bugs and the AI struggled to solve them. Rewriting in C# seemed a lot more robust. I use it a lot these days and I find the AI rarely has any issues with language/framework and you get pretty good results.

by bensyverson10 hours ago|

parent|

prev|

[-]

Yeah, C# is probably the closest direct comparison. I like that Go emits a simple binary, whereas it seems like that needs to be configured with a .NET project. Probably just a matter of taste/preference!

by afdbcreid15 hours ago|

prev|

[-]

I wouldn't call Go's type system "good". It's basic or less. It's sound, at least (in the presence of data races), but that is the case (or mostly the case) for most programming languages.

by frizlab14 hours ago|

prev|

[-]

SwiftUI has nothing to do with Swift… It’s just a UI framework that happens to have been written for Swift.

by bensyverson10 hours ago|

parent|

[-]

Fair—though SwiftUI has influenced/required new Swift features like Result Builders. I've found generating Swift to be a mixed bag. The LSP consistently reports stale errors which the model has to ignore, handling strict concurrency correctly can lead to ugly workarounds or huge refactors, the documentation for Apple's APIs aren't accessible to agents, the list goes on.