Java does not have versions baked into the language except for for class formats, which change rarely and are upwards compatible with new JDKs. Package versioning nowadays is handled by tools like maven and gradle. It's a good separation of concerns that keeps Java from being even more complicated than it already is.
If the concern is with handling interface versions, why not just use loosely coupled web services?
Actually the version dependency is undpecified. One has to guess it by trying to compile. I don't think aliasing package names solves this.
You tell me that java tools take care of it. So go tools could take care of it. But this requires that the info is provided in a standard and clear way. This info can be kept optional for backward compatibility. Without this info, we are limited when trying to use go for bigger projects.
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").
You cannot separate both issues. Go assumes all API are immutable which is insane, a package manager won't solve that.
Having the version in the package name is useful, as an incompatible API change usually requires visiting the code and this forces the issue.
It definitely eases the problem, like proper dep mgmt would, but not more... ;)
What's preventing a tool like pip, npm, or stack from working with Go for versioning?
Go is designed so that we have to assume that an API and the compiler are either perfectly backward compatible or immutable. This is a simplification inherited from C and other programming languages.
If we want to support changing an API, then we have to specify version along the package name and import statement. Some packages already do that but it isn't satisfying because it is hardcoded in the package name.
I like the versioning rule chosen by ICE from zeroc. A version is not backward compatible with other versions. A release must be backward compatible with previous release of the same version.
So it should be possible to specify a version and release for packages in import statements which specify that the specified release and all subsequent release are valid.
Dub, for the D programming language is going that line of direction.
I'm aware that it may create a dependency hell. But it already exist and is hidden. The alias hack is not a good solution. It will make things worse by making the rules more lax.