Toward Go 2 (or D needs to collect experience reports)

[Jesse Phillips via Digitalmars-d]

On Wednesday, 6 September 2017 at 14:42:20 UTC, dimaria wrote:
> 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 think D is already following those principles as it improves on 
D2's bugs and features. I think this is the right approach for D 
at this time. But re-evaluating what D3 should mean every couple 
years makes sense but will always have the thought that it is 
another D1/D2 split.