> I guess I shouldn't be promoting language-bashing, but +1 for calling Go an unacceptably crippled edifice :)

https://old.reddit.com/r/rust/comments/dh4rcz/my_favorite_ru...

I often see Go functions with a large number of lines- many of which are noisy boilerplate error handling. Combine that with terse variable names, type inference and it's straight up tiresome to filter out the important parts. These functions aren't even doing all that much.

There is a healthy middle-ground between excessive abstraction a la Enterprise Java and what Go offers.

There are nice aspects to reading Go, but any function which does some kind of error-prone operation is so hard to grok, it gets tiring - the actual purpose is constantly interrupted by 'if err := nil' so much.

And gods help you if there is some actual non-trivial error handling going on, as you've generally learned to gloss over and can easily miss that one place that actually does something with an error other than log and return.

Also, while admittedly rare, trying to review code that needs to copy structs around, if they also involve pointers or slices, is just hell.

I'm sorry but I couldn't read past this.