On the other hand, most pieces of software in this world are kind of mediocre code written by unmotivated employees within tight timelines.
replyIn such context, I think Go might be a better or at least, more realistic, compromise in most cases.
If you have unmotivated employees then using Go will only exacerbate the shortcomings it has. Cutting corners is much easier in Go than it is in Rust. But in general it's true, if you want a piece of code released a bit faster but spend more in developer hours maintaining it later than Go is the better fit. And there are definitely use cases for that.
replyYou can write exploratory code in Rust fairly quickly, it's just obvious when you've done so due to the heavy boilerplate involved. Keep in mind that the earliest versions of Rust were actually very Golang-like, the language iteratively evolved towards what it is today.
replyThis article convinced me to switch from Go to Rust: https://discord.com/blog/why-discord-is-switching-from-go-to...
replyThe issues with Go in that article only surfaced at Discord scale.
reply