2 ms·
> forced the developer to adopt a specific folder organization Well, so does C (and basically everything else). Alternatively, you can pass tons of -I and -L f
by slrz 8y ago
> forced the developer to adopt a specific folder organization
Well, so does C (and basically everything else). Alternatively, you can pass tons of -I and -L flags to your compiler calls but you can do that with Go, too.
The point of GOPATH was to make this unnecessary because everything can be deduced from the source code and its location within the file system.
- sigjuice 8y agoYou have it backwards. C doesn't restrict where I can keep my source tree.
- jrockway 8y agoI mean, the C toolchain has plenty of baked-in paths where it expects to find something. If project foo depends on project bar, project foo is not automatically going to look at ../bar when building. You either set that up manually, or you put everything in /usr/include and /usr/lib. "Set that up manually" usually consists of an m4 script that takes 15 minutes to run as it tries to look for all the dependencies ("./configure"). It's flexible, but it's not great.
- mathw 8y agoBut at least that makes it no harder to ask for a specific version of something. Go not having version locks for dependencies by default is a major failing. Fortunately it looks like that will be changing.