4 ms·
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
by oelmekki 9y ago
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.
- bonesss 9y agoAre we too early for "Go-2 considered harmful" jokes?
- tmaly 9y agoThere is always the possibility that a go fix tool makes a transition to version 2 super simple.
- oelmekki 9y agoIndeed. I didn't think about that, but given how gophers are into code generation, this could happen.
- remus 9y agoThe 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.
- oelmekki 9y agoAwesome. Does anybody here know where this discussion happened, for further reference?
- jen20 9y agoI believe the "official" start of the discussion was on the Go blog [1]. [1]: https://blog.golang.org/toward-go2 https://blog.golang.org/toward-go2
- oelmekki 9y agoIndeed, 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.