Very interesting article: https://blog.golang.org/toward-go2

The highlights:

> Our goal for Go 2 is to fix the most significant ways Go fails to scale.

> Go 2 must bring along all those developers. We must ask them to unlearn old habits and learn new ones only when the reward is great.

> Go 2 must also bring along all the existing Go 1 source code. We must not split the Go ecosystem. Mixed programs, in which packages written in Go 2 import packages written in Go 1 and vice versa, must work effortlessly during a transition period of multiple years. We'll have to figure out exactly how to do that; automated tooling like go fix will certainly play a part.

> Today, what we need most is experience reports. Please tell us how Go is working for you, and more importantly not working for you. Write a blog post, include real examples, concrete detail, and real experience. And link it on our wiki page. That's how we'll start talking about what we, the Go community, might want to change about Go.

I believe that if we ever want to see D3, we should start a similar process and collect real world feedback about things that are annoying on a daily basis.
There have been many threads about "I want to have feature X" in D and of course legendary threads like the one about removing auto-decoding, but the aim of this discussion is to identify things that bother you frequently or prevent you from using D on a wider scale.
Please see Russ's post for good examples. Blog posts or reports on the wiki are very welcome.

The one thing I got from that blog post is that the HN and reddit discussion was overwhelmingly about generics, and how the Go leadership seems to not give a damn about what its user community wants...

On Sat, 2017-07-15 at 04:29 +0000, Matt via Digitalmars-d wrote:
> The one thing I got from that blog post is that the HN and reddit discussion was overwhelmingly about generics, and how the Go leadership seems to not give a damn about what its user community wants...

On the other hand, I wonder how many practicing Go programmers actually care about things such as HN and Reddit?

On the Go mailing lists, generics comes up every so often and the thread dies a death quite quickly. I think the view that "there is no sensible semantics for generics that work with Go, and we have interface anyway" has been accepted by the Go community at large. There is also go generate.

-- 
Russel.
=============================================================================
Dr Russel Winder     t:+44 20 7585 2200   voip:sip:
russel.winder@ekiga.net
41 Buckmaster Road   m:+44 7770 465 077   xmpp:russel@winder.org.uk
London SW11 1EN, UK  w: www.russel.org.uk skype:russel_winder

On Saturday, 15 July 2017 at 02:55:42 UTC, Seb wrote:
> Very interesting article: https://blog.golang.org/toward-go2

Good read, thanks for posting. I also thought the discussion under "Explaining Problems" was really well done. A couple of lines from that section:

> Convincing others that a problem is significant is an essential step.
> ...
> When we disagree about whether to adopt a particular solution, we're often actually disagreeing about the significance of the problem being solved.

The author is trying to motivate the importance of experience reports, but is also describing a common and challenging problem in software development environments.

--Jon