I feel like stepping in a field full of landmines when reading through almost every single line of Go code.
Conversation
How so ? I thought Go was known for its simplicity.
2
It's easy to learn if you know similar languages, but there's lots of complexity hidden in there.
1
I don't really know Go. Do you have specific examples ?
1
Stuff like avoiding data races, nils behind interfaces, the way it represents potentially erroneous data using pairs as opposed to disjoint unions, remembering to check for errors, how you need to be conscious of default values and data initialized in an invalid state…
1
1
Sorry if that sounds a bit ranty. Just found it rather frustrating to use, but you might find it works well for you.
1
I'm just curious (as I said, I've never used go beyond an hello word).
Given that I use c++ most of the time, my threshold for minefields is rather high.
1
Yeah, it's pretty obvious that the designers were coming from a C perspective and their threshold was quite high too. Just hoping people learn over time that programming doesn't need to be this janky. I think that's happening, but it's a slow process. 😅
Fasterthanlime has a some blog posts that go into more depth on some design issues that I also struggle to accept:
- fasterthanli.me/articles/i-wan
- fasterthanli.me/articles/abstr
Perhaps in the context that Go was designed (server infra) this stuff is ok, but it seems kinda clunky to me.