> Packages and modules should never be reliant under an assumption about the underlying file system They are not. Import paths are not part of the language, th

> Packages and modules should never be reliant under an assumption about the underlying file system They are not. Import paths are not part of the language, they are interpreted by the go tool. The only relation to the filesystem is that by using the go tool, you will get a directory hierarchy that seems to match import paths in the sense that that in foo/bar you will have a bar directory child to a foo directory. This is very useful to developers, it means they can find their files, but you could build a conforming build tool that keeps files in SQL, if that's your thing.