3 ms·
Versioning is not going to fix go's namespace problem, unless the package manager does the aliasing, like in every other well crafted language. Go namespace fea
by aikah 10y ago
Versioning is not going to fix go's namespace problem, unless the package manager does the aliasing, like in every other well crafted language. Go namespace feature is completely broken, URL shouldn't be namespaces. This is yet another half backed feature put in Go that doesn't scale in practice. There are so many of them in the language, they'll be more and more obvious as the language gains adoption.
- chmike 10y agoVersion conflicts and package naming collisions are two different problems. The OP referred to the version problems. I overlooked package naming conflict which can occur with composed package names. It is true and correct that aliasing will help solving such type of problems. Thanks to point this out. PS: I suspect you have been down-voted because your critic is excessive (cf. "half backed feature").
- aikah 10y ago> Version conflicts and package naming collisions are two different problems You cannot separate both issues. Go assumes all API are immutable which is insane, a package manager won't solve that.