One thing that I like about Go is that it's easy to write good Go code, and it stays good for a long time without maintenance. So long as you're not trying to be clever, your code will probably be idiomatic and concise, and the language doesn't really change so it'll be useful for a long time.

Even my worst Go code is really not that bad

My many thousands of coding GOTO's is really not that bad either

@sir the biggest selling point that got me using go for small "complex" tools is how *easy* it is to deal with channels and coroutines.

Most languages have some form of message bus facility now but go really managed to make it dead easy to get right and pretty hard to fuck up.

@sir Shows that Go managed to respect the 10 years old rule.

@sir What do you think about the package management story? 3ish years ago I shipped something in go and was relatively happy until I changed OSS and forgot to grab my godeps dir and had to completely rewrite it because a dep I used changed entirely.

I ignored the recent drama and I'm wondering if we're fixed now?

@sir right I had no clue what I was doing then :P.

Did they fix it or is it still "operate like google or not at all"?

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!