Felt in love with golang ♥️.

Why?
It seems like golang designers are totally isolated from what's been happening in the last 30 years in languages design.

Google it for more xd

@SevenDeadlyBugs what about JS's new "optional chaining"? Sure it's trying to fix only it's problem, but it can create more readable scripts in the future.

Until?

Go is designed really well in my opinion. The bare minimum amount of keywords and yet provide a full featured language that does concurrency well is admirable.

When in doubt leave it out!

Simplicity, syntax and language itself. Just that

Was not go safe C?

@aviophile That was not the primary goal at all. It was supposed to be a fast compiled language that also compiles really fast and can handle concurrency well (like event based webservers like nginx). One of first thing it did and was designed for was replacing the C++ dl.google.com which handles a lot of concurrent downloads. They had massive issues with the C++ compile times on every change.
But yes it also has common modern safety features build in.

You are welcome. And i mean the gopher is the best logo ever for a language!

It's a cute language, if you don't need generics, a reasonable error handling system, or type safety.

I kept running into walls, and eventually found the learning curve on Rust to be easier -- maybe that's just my silly brain though.

I actually found crates like Rayon and Crossbeam to be more intuitive and liberating in the long run than goroutines. 🤷‍♀

Ah yes. Behold the syntax monstrosity:

go func(msg [5]int) {
// Do something
}([5]int{0, 1, 2, 2, 4, 5})

I admire you guys for loving that language. Every one should use what fits them well. I was trying to overcome that issue with go but it ends with failure in about two weeks.

PS Hope you are not mad, I was just curious why you like it :)