What is the idea behind Go package naming convention?
go, naming-conventions
Solution
You can use `howeyc/fsnotify` if you want to. When `github.com/howeyc/fsnotify` is used it's understood that the package is hosted on Github. Other repositories work as well.
The reason is it makes it easier to locate and install dependencies with `go get`. Otherwise you'd have to satisfy the dependencies manually. And since forking repos is quite common in the open-source world, you may have a modified version from the same author. So it helps to distinguish what your project depends on.
Problem
I'm trying to understand the idea behind package naming convention in Go. Most packages are installed and imported as something like: ``` import "github.com/howeyc/fsnotify" ``` I get the idea that package names should be unique, but I don't see the point of using the website `github.com`. Why not just use `author/package`? Like: ``` import "howeyc/fsnotify" ``` That's not likely to ever collide. Or some other "shorter" strategy? Is it because it "just works" with `go get`? Or is there some other reason?