> On Jul 16, 2020, at 3:35 PM, Ian Lance Taylor <i...@golang.org> wrote: > > The language is stable and is not looking to change in any > significant way (except perhaps for adding generics). We've realized > that we need to be upfront about that.
The Go2 process certainly created the expectation that the language was looking to change. But I guess the point here is that this window is now closing? Maybe it would be good to have a new blog post to that effect? Expectation management is very important -- if we all recognize and accept that Go is a fixed language that will never change, then nobody will be disappointed when it doesn't! And why should it change? This idea that languages should constantly be evolving may not make any sense: once a language is Turing complete, and highly effective, supporting millions of happy, productive coders, it could just be done. People can invest time and energy in writing code and tools, not changing the language. I guess the only two major pain points that are widely discussed are generics and error handling, and it looks like we'll get a good solution for the first, and who knows about the second at this point? Maybe the ONLY allowed issues going forward should be experience reports and clear identification of problems / pain points (which have always been requested, but are probably the minority of user contributions?), and maybe some process for community input / voting for how significant those issues are (as Max suggested). - Randy -- 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/73C21F61-EC5E-4649-A3C8-61354317A005%40colorado.edu.
