3 ms·
But is that really bad for Go? I'm not sure it is. Go1 will always be useful just as it is.
by _wldu 6y ago
But is that really bad for Go? I'm not sure it is. Go1 will always be useful just as it is.
- mseepgood 6y ago> But is that really bad for Go? No, I don't think so.
- cpuguy83 6y agoI don't think the op intended "storm" to be negative here. Just to say that there are loads of changes coming soon.
- throwaway894345 6y agoOne of the features of Go is that everyone writes code the same way, which means anyone can easily read anyone else's code; there's only one paradigm; idioms and conventions are strong across the community. This property exists precisely because Go isn't very expressive, but the generics proposal will make Go more expressive and in all likelihood the ecosystem will become more diverse accordingly. Whether this is a positive or negative depends on how much you value expressiveness versus standardization.