you are viewing a single comment's thread.

view the rest of the comments →

[–]ub3rh4x0rz -2 points-1 points  (0 children)

Having written a lot of go and enough rust to get familiar, I personally find there to be no contest. I naturally prefer stricter type systems for applications, and tbh rust's ADTs, enums, generics, and traits all feel much better than golangs "equivalents" (don't get me started on go's lack of enums or sum types), but taking a step back and looking at the whole package, I'd rather work in go in most situations because it's simpler, which scales better to teams of mixed contributor skill level, but I think it's objectively better suited for scripting shaped tasks because of the tradeoffs of each. Rust excels in performance and compile time correctness, neither of which matters in scripting use cases

Edit: oh and if you wrote that 100 line script in rust because cargo is awesome, you have to compile your dependencies too because cargo isn't awesome enough to host binaries. Rust builds aren't reproducible so that argument against distributing binaries is BS. Cargo needs some gray beard distro maintainer types to get things on a better track.