I prefer vendoring since it doesn't rely on a 3rd party being online or existing in a year. Also it's simpler when you want to have repeatable builds, since the vendored code is usually in your repo. It's also convenient for CI/CD things, since your repo ships as a unique component.
Also using versioned path like that means that a version bump means editing all your files. Across a large project, it becomes harder to manage.
However, versioned path aren't incompatible with vendoring tools. So one doesn't prevent the other.
FWIW, I think versioned path is also not very popular in the pseudo-contest of vendoring code/versioning path.
I wanted to let you know that I agree .v0 is strange. I see that now and it was an oversight. We're changing it from v0 to dev now instead:
import "azul3d.org/audio.dev"
No worries though, v0 will continue to work for backwards compatibility.
Track the issue: https://github.com/azul3d/issues/issues/10
v1 (latest version)
import "azul3d.org/audio.v1"
v0 (in development)
import "azul3d.org/audio.v0"
Is this normal for go packages?