On Thu, May 23, 2019 at 8:50 PM <lgod...@gmail.com> wrote: > > Ian: I find many of your comments related to how the Go team functions very > interesting, > I for one would find it helpful if 2 or 3 times a year the Go Team would > communicate to the Go community at large, information related to where and > in what direction(s) it is taking Go, and what directions the team has > decided NOT to take Go . > > I think the idea of a relatively small team of people deciding what Go will / > will not morf into, is a sound one considering the what goes on within the > C++ world, > > I also think it important that the Go team utilize some mechanism for > screening input from the Go user community regarding changes / enhancements > to the language, new packages etc. > > An important measure of Go's value as a useful language is measured by the > size of Go user community, which in my opinion is very much related what Go > offers developers to make their life easier vs other languages.
Thanks for the note. We do try to communicate plans for the language and standard library packages, broadly on the Go blog and more specifically on the golang-dev mailing list. E.g., https://blog.golang.org/go2draft, https://blog.golang.org/go2-here-we-come . Naturally it's a lot harder to say which directions the team has decided not to take Go. One way to see that is to follow the issue tracker for bugs marked Go2 (https://github.com/golang/go/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Ago2). That is a list of changes either rejected or still being considered. Of course, a rejected issue doesn't always mean that some similar change will not be adopted; sometimes it only means that that particular change is rejected, but a different, better change that addresses the same problems might still be accepted. I don't really see a benefit to a broader announcement of ideas that we aren't going to do. For one thing, it might change. In general we are always interested in hearing new proposals for changes, using the proposal process described at https://golang.org/s/proposal. Of course, before writing a new proposal, it helps to look to see whether there are similar previous proposals. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcVaQCD4A%2BBcLyT3Cy%3Dv5eBmiLuMDZq9ii_jvU2X8S4JmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
