Gotards in 2011: nooooo generics are the devil

Gotards in 2020: generics are still the devil, but at least we are not retarded.

https://blog.golang.org/generics-next-step

>>2
Yeah, fast compilation is good, cross compilation is good. 2 points for Go there.

But a lot of it is shit. The designers punted on basically everything that seemed too hard or might've added expressivity. So the language is full of un-composeable features and weird dead ends that make no sense.

Cool: a function can return

(string, err)

. so that must mean Go has some notion of tuples, right? And I can use multi-valued expressions in other contexts? Haha, no.

This

for i, v := range {}

loop seems nice, how do I get my data structure to implement that? Can't. Okay.

Sometimes Go gets close to the right answer, but then goes out of its way to fuck it up. Errors are return values? Fine. Now how do I avoid this retarded

if err != nil

boilerplate everywhere? Can't. Okay… how do I ensure that errors aren't ignored by mistake? Can I use an option type and force callers to handle every case? Nope: the type system is just too nerfed and broken.

Don't even get me started on the cargo cult that guys like Rob Pike have inspired. It never ceases to amaze me how much of the Go community will get on board with whatever vague handwaving sophistry issues from his Canadian gob. It's like he's running a massive psychological experiment in cognitive dissonance:

• "Exceptions are bad, exceptions are bad…" but then Go has

  panic

  /

  recover

  which is like… the same fucking thing
• "Errors are values, errors are values…" yet it's endemic in Go to return useless errors that encode no information at all. Like

  error.Errorf("File not found: %s", path)

  forcing clients to parse a string instead of returning a proper struct.

Go has spawned a community of troglodytes who would rather cling to C's dusty corpse than engage with the last 4 decades of language research.

GO IS PIG