an alternative to GOPATH with integrated support for versioning and package distribution
Right, after saying no one needs them for years. ;)
Was it really the case? From Russ first post on vgo/modules:
It was clear in the very first discussions of goinstall that we needed to do something about versioning. Unfortunately, it was not clear, at least to us on the Go team, exactly what to do. […] This ignorance of package versioning has led to at least two significant shortcomings.
All the problems about versioning are orthogonal to goinstall.
They are fundamental to any system in which you’re using
multiple code bases that progress independently.
Solving that problem is explicitly not a goal for goinstall today.
I’d be more than happy for goinstall to solve the versioning
problem later, if we can figure out how.
I am not dismissing the problem. I just think it is difficult and
not any different for goinstall than it is for any other software
system.
I do have to admit that I haven’t checked what authors say about it, I’ve only seen Go users defending lack of library and version management. I’m glad to see that they weren’t opposed to it.
I mostly stopped watching after they went to implement polymorphic data structures by silently downcasting to interface{} after saying no one needs polymorphism.
Yay! congrats to the folks working hard to make this happen!
So not that modules are in go is, to quote Brad Fitzpatrick, asymptotically approaching boring. There’s only the (right now, hypothetical) Go2 bike-shedding to be a big release in the future!
Kidding aside, I’m excited about more wasm in this and future releases and looking forward to some boring xml stuff in 1.12.
Right, after saying no one needs them for years. ;)
Was it really the case? From Russ first post on vgo/modules:
And when you read that linked thread you will see that Russ agrees that versioning is needed:
I do have to admit that I haven’t checked what authors say about it, I’ve only seen Go users defending lack of library and version management. I’m glad to see that they weren’t opposed to it.
I mostly stopped watching after they went to implement polymorphic data structures by silently downcasting to interface{} after saying no one needs polymorphism.
There are plans (see couple of next slides) to provide facilities for static polymorphism for Go2.
Yay! congrats to the folks working hard to make this happen!
So not that modules are in go is, to quote Brad Fitzpatrick, asymptotically approaching boring. There’s only the (right now, hypothetical) Go2 bike-shedding to be a big release in the future!
Kidding aside, I’m excited about more wasm in this and future releases and looking forward to some boring xml stuff in 1.12.
Congrats again!