GOPATH mode does *not *limit your Go code to a single directory. I've seen
this misunderstanding stated in probably hundreds of various posts.

$GOPATH allows specification of multiple directories.  I've used that
capability for several years to distribute my Go code to my personal
general library and to various application-specific libraries. Each of the
multiple GOPATH directories refers to a Go "workspace", so the result is my
general library workspace plus mini-workspaces in various application
directories -- each with src, pkg, and bin subdirectories. A single go
install installs all workspaces specified in your GOPATH at once, or you
can selectively build by temporarily changing the GOPATH.

This is a pretty good setup for me, a decades-experienced software engineer
working in "programmer" mode for my personal development.

Go's goal of ending GOPATH mode sounds like a choice to serve the
professional software engineer, and not the personal programmer. Module
mode is a good thing if you are publishing your code, but is a lot of
additional labor and cognitive load for us "programmers".

I wonder if this might discourage adoption of Go by certain categories such
as college and high school students, non-software-engineer professionals
who write internal programs for their business, and curious folks who want
to introduce themselves to Go. It is soooo much easier to set up my
environment with GOPATH mode. In attempting conversion to MODULE mode, I've
spent lots of frustrating hours and it's still not working perfectly!

So, I am +1 for retention of GOPATH mode (as well as MODULE mode), allowing
Go users to make the choice of MODULE vs. GOPATH based on their needs.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAKyHfRPYgop6YPgk3AcJ4Q43NgV%3D9KP%3DzgYja8Z6FJuc0UuPig%40mail.gmail.com.

Reply via email to