3 ms·
Being boring really is what I love most about Go. It doesn't change much and there is a culture of simplicity, so it's quick to onboard new devs and there isn't
by grey-area 6y ago
Being boring really is what I love most about Go. It doesn't change much and there is a culture of simplicity, so it's quick to onboard new devs and there isn't a lot to get your head around. That also makes it good for building large projects, as the complexity is in the domain and the application, not clever uses of the language itself.
I almost wish they'd make it more boring and take a few things out, but it's probably too late now to change the language much and people would complain vociferously. Things I never use and wish it didn't have: panic, goto, labels, struct tags, executable comments, even arrays.
The only things I'd like to see improved significantly are enums, errors, and user-space generic collections (coming soon!).
- cy_hauser 6y ago> generic collections (coming soon!) You and I must experience time differently. I read a couple days ago that the end of 2022 would be the earliest they might appear but probably further out than that.
- leetrout 6y ago> the earliest that generics could be added to Go would be the Go 1.17 release, scheduled for August 2021 https://blog.golang.org/generics-next-step https://blog.golang.org/generics-next-step
- grey-area 6y agoI've been using it about 8 years at work, and don't mind if they take another year, it'll take a while to work into large code bases anyway. Personally I've felt generics as a lack but not a huge unfillable hole, and prefer language stability to churn, so am completely fine with it taking time to add large features. I'm pleased with the evolution of the generics proposal so far - it's getting simpler and more transparent. I really wish in their mooted Go 2 they could just remove some features, as listed above, rather than add some. Perhaps everyone prefers a slightly different subset of the language though so that isn't really possible.