3 ms·
Rust code generation consumes lot of token Go is much better target, i've observed rails/ruby code is also much easier for AI to spit out. And Haskell flies w
by faangguyindia 5mo ago
Rust code generation consumes lot of token
Go is much better target, i've observed rails/ruby code is also much easier for AI to spit out.
And Haskell flies with AI
- jgilias 5mo agoYes, but it comes with much better “built-in” guardrails to rein in the autocomplete. Especially if compared to something runtime-surprise-prone-if-lovable like Ruby.
- faangguyindia 5mo agoThis is why I suggested Go. Rust doesn't add anything over Go for LLM coding.
- jgilias 5mo agoBut it does. A whole class of runtime errors you can trivially produce in safe Go — null pointer dereferences, unchecked type assertions, missed enum cases — are unrepresentable in safe Rust. Also, the type system is a lot more expressive, so more invariants can be encoded in it, leading to more business logic bugs being caught at compile time rather than in production.
- pjmlp 5mo agoFor that I would chose neither, rather go with Haskell, OCaml, F#, Lean, Dafny, FStar, Scala, Kotlin,...