<p>Do we have a rough timeframe when we can expect Go 2? 2 years? 5 years?</p>
<hr/>**评论：**<br/><br/>chewxy: <pre><p>Seriously, just watch the talk. Russ is saying we need a way to plan for go2. Like in most things, one must define the problems before jumping into a solution. </p></pre>bitmadness: <pre><p>I watched it lol. I agree we need a plan. Part of having a plan is having a timeframe in which you intend to execute the plan, hence the question.</p></pre>chewxy: <pre><p>Russ did mention that if Go 1.20 is good enough to be called Go 2, it'll be called Go 2...</p>
<p>Go 2 as such, isn't really much of a concrete goal, IMO</p></pre>dlsniper: <pre><p>It's official! Half-Life 3 confirmed! 1.20 means 1 2 0, means 1+2+0, means 3, right there! And since we know Go 1.20 will be released in 2022 that's another hint right there: (2+2+2)/2 = 3 and there are 3 2's in 2022. So Half-Life 3 is confirmed for 2022!</p></pre>bitmadness: <pre><p>Why the downvotes? I asked an honest question and I get downvoted. Makes me sad for our community...</p></pre>shovelpost: <pre><blockquote>
<p>I watched it lol.</p>
</blockquote>
<p>Probably because you said you watched the talk and yet in the talk Russ specifically mentioned Go 1.20.</p></pre>BurpsWangy: <pre><p>It's currently not even on the milestone...</p>
<p><a href="https://github.com/golang/go/milestones" rel="nofollow">https://github.com/golang/go/milestones</a></p>
<p>So, anybody's answer would just be a guess.</p></pre>mzupzup: <pre><p>With the (imo very sane) approach to Go 2.0 suggested by Russ Cox, is the timeframe even relevant?</p>
<p>If the transition is smooth and step-by-step with community inclusion, there should not be a "switch or get left behind"-period.</p></pre>__CAFxX: <pre><p>Hold your breath :) </p></pre>
