> The point is that the primary intention of Go is to push developers to write the most readable (and hence, maintainable) code possible. Lack of parameterized

> The point is that the primary intention of Go is to push developers to write the most readable (and hence, maintainable) code possible. Lack of parameterized types leads directly to code-duplication. How is duplicate code more maintainable? > The problem is that once you give people parametrized types, they're going to parametrize the shit out of them, leading to byzantine messes such as the C++ standard library or Boost. An extraordinary claim with no backing what so ever. Just because C++ turned out terrible doesn't mean everything else has to. Look to C# and Java. They're doing just fine. Also: how is littering your code with "interface { }" any less Byzantine than simply using "T"?