Go: Six months in

#go #programming

Go is a mixed bag
Its possible to write elegant go
The go community doesn't want you to
If you do, you might regret it, and end up deleting it all
if err != nil was invented by evil monkeys that get paid by scrollbar pixel movement
if err != nil will seriously save your bacon
In many languages, the standard library is a good place to look for examples of good code
In go, the standard library encourages many practices I have, over the too many years, come to consider harmful
I am learning to question my beliefs, but it hurts really bad, and I'm not always wrong
Go docs are syntax references, not docs
Go docs assume too much prior knowledge
There are some foundational Go essays that are absolute gold
Ardan Labs has some killer go content and doesn't assume you know it all already - no affiliation, just mad respect
Many well respected go experts seem to believe in copy paste coding
This makes me want to vomit locusts
Gophers really hate dependencies, which leads to the aforementioned copy pasta
Not managing tons of lib dependencies of your own making is really liberating
I'm learning to eat locusts, but sometimes cotton candy is better
Go mod needs a UX/DX designer to join the team badly
Go mod's job is hard - so that's not a criticism as much as a real hope

Top comments (3)

Ardan labs content is real nice thanks for sharing. Never knew about them before

if err != nil was invented by evil monkeys that get paid by scrollbar pixel movement

This was epic :-D

Thank you :)