News for hackers. Stuff that matters.
Re:Go 1.10 Beta 1 is released by oelmekki on Friday December 08, 2017 @08:40AM (#15878526)
My biggest fear being that go-2 may be a major break, like symfony-2 and angular-2 were (as examples).

Running old code and having it "just work" is something I really love with go. I hope go-2 new features won't come at the cost of breaking old code.

Re:Go 1.10 Beta 1 is released by bonesss on Friday December 08, 2017 @08:58AM (#15878626)
Are we too early for "Go-2 considered harmful" jokes?
Re:Go 1.10 Beta 1 is released by tmaly on Friday December 08, 2017 @09:31AM (#15878790)
There is always the possibility that a go fix tool makes a transition to version 2 super simple.
Re:Go 1.10 Beta 1 is released by remus on Friday December 08, 2017 @10:12AM (#15879135)
The maintainers have already publicly stated that this will be the case. They used python 2 to 3 as an example of what they're NOT going to do.
Re:Go 1.10 Beta 1 is released by oelmekki on Friday December 08, 2017 @10:18AM (#15879188)
Awesome. Does anybody here know where this discussion happened, for further reference?
Re:Go 1.10 Beta 1 is released by jen20 on Friday December 08, 2017 @10:22AM (#15879238)
I believe the "official" start of the discussion was on the Go blog [1].

[1]: https://blog.golang.org/toward-go2

Re:Go 1.10 Beta 1 is released by oelmekki on Friday December 08, 2017 @10:27AM (#15879278)
Indeed, thanks.

Here is the relevant part from it:

> 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.

Re:Go 1.10 Beta 1 is released by oelmekki on Friday December 08, 2017 @10:02AM (#15879052)
Indeed. I didn't think about that, but given how gophers are into code generation, this could happen.