> Go looks like it has been designed into a corner, but it is too late to back up now.
Not really. We had years of experience with Go—and made many changes—before we stabilized the spec with Go 1. We are happy with the major decisions we have made so far, as are a lot of Go users. Of course there are minor things we would change if given the chance today, but the basics of the type system and the presence of nil pointers are not among them.
The reason generics is hard is because we want to find a way of doing it without losing the feel of the language we have right now (which we quite like, thanks).
Not really. We had years of experience with Go—and made many changes—before we stabilized the spec with Go 1. We are happy with the major decisions we have made so far, as are a lot of Go users. Of course there are minor things we would change if given the chance today, but the basics of the type system and the presence of nil pointers are not among them.
The reason generics is hard is because we want to find a way of doing it without losing the feel of the language we have right now (which we quite like, thanks).