It's not about how hard or easy the code is to write, at all. Any line of code you don't write, is a bug you didn't write either. I worked on a significantly s

It's not about how hard or easy the code is to write, at all. Any line of code you don't write, is a bug you didn't write either. I worked on a significantly size go codebase and the number of stupid bugs that popped up, like bad loops instead of a simple `filter` function, were just silly. Having all this memory safety and other stupid bugs ruled out but not map, filter, or reduce just felt lazy on the Go authors part. Of course, now that a member of the go team has said it, we'll see a huge shift in what the go team thinks about generics. I'm glad I don't deal with the go community anymore.