See also iterators. Maybe one day string interpolation and ergonomic error handling?
That said, there does seem to be a minority of people who want to tear iterators and generics back out of Go. And people who stumble into /r/golang asking for features common in other languages often seem to get answers along the lines of "just use those other languages rather than try to change Go".
So the more people who use Go, the more people will be frustrated by its shortcomings _and_ by the people complaining about its shortcomings.
So I wind up with the impression that what would make both the most gophers and non-gophers happy is to avoid proselytising like that blog post.
I think with the old guard leaving Google, Go might pick the pace of introducing long-requested language features. At least it looks like more proposals are being taken seriously as of late.
The actual truth is, that the choice of language/stack should be completely and solely based on the knowledge of people that work at the company and should practically boil down to 2 or 3 languages with 1 framework and as little supporting technologies as possible.
16 Comments
programming-ModTeam@reddit
Successful-Money4995@reddit
syklemil@reddit
PerkyPangolin@reddit
PerkyPangolin@reddit
AvidCoco@reddit
blazmrak@reddit
JennySlopez@reddit
PerkyPangolin@reddit
BayouBait@reddit
blazmrak@reddit
le_bravery@reddit
tomster10010@reddit
who_am_i_to_say_so@reddit
CanvasFanatic@reddit
SpeedDart1@reddit