@kirby @dcc @Kirino I am a programmer and have coded in many languages over many years.

There is a very, very good reason why, among the next-gen languages, Go is far more widespread than Rust, despite Rust creating programs that run far faster without any garbage collection.

At the end of the day, practical coding is about *doing*. With Rust, you're going to spend probably about 95% of your time reading documentation and learning about edge cases. This does NOT change as you learn more; due to the complexity of the language and how it continuously changes, there will always be far more learning than doing.

Go, on the other hand, rarely changes significantly, and it intentionally has a simple syntax. This leads to its own quirks and lack of certain functionality, but someone who just wants to get the job done can work with Go far more easily, and more importantly, work on *other* people's code more easily. There really aren't that many examples of "awful" Go code, whereas with Rust you can pretty much pick any popular library and find cryptic code that would take hours to reverse-engineer, let alone the time to actually contribute to or modify it.

That, and every profile picture of a Rust developer is a disgusting tranny.