5 ms·
Interesting, so "go 2.0" is 2 years down the road, it will be interesting to see what happens next.
by aikah 11y ago
Interesting, so "go 2.0" is 2 years down the road, it will be interesting to see what happens next.
- vanderZwan 11y agoThat's not how semantic versioning works[0]. If they want (and everything still points in this direction AFAIK) they will just keep releasing Go 1.10, 1.11, 1.12, etc. http://semver.org/ http://semver.org/
- zellyn 11y agoAccording to Ian Lance Taylor's recent post, there are no current plans for go2: https://groups.google.com/forum/#!topic/golang-nuts/ydeLGm2SYfQ https://groups.google.com/forum/#!topic/golang-nuts/ydeLGm2S...
- iends 11y agoWhere did you get this idea?
- omginternets 11y agoI think 2.0 implies breaking backwards compatibility, which the Go devs have opposed on principle.
- sudhirj 11y agoI seriously doubt that - what they have clearly opposed is breaking backwards compatibility in Go 1.x - they day they decide to break backwards compatibility is the day work begins on Go 2.0
- omginternets 11y agoThat's... what I just said...
- PopsiclePete 11y agoThere is no Go2. Go2 is not a "thing", it's the absence of another thing. It's very Zen. Go2 is everything that Go1 cannot be. If Go1 was the universe, Go2 would be everything outside of it - which is nothing. Anytime someone mentions "This needs to wait for Go2", what they mean is "We can't do this now due to the Go1 compatibility promise, so let's leave it for the far future, for a day that may never even come, and table this discussion".
- mseepgood 11y agoThat's not how version numbers work.