I realized one factor that might play a role. I came primarily from a C++ background, and back then, stackoverflow and google were paramount and used daily.
Now that I'm primarily using Go, I almost always get my answers from godoc.org (i.e., the documentation of packages), from source code, from the specification, and from trying things on playground. I don't remember using stackoverflow for Go programming questions in years, if ever.
I wonder if that's a property of Go language (great docusmentation, easily readable source, referenceable spec and viability of answering questions via playground experiments) that cause this, and if it applies to other people too.
I realized one factor that might play a role. I came primarily from a C++ background, and back then, stackoverflow and google were paramount and used daily.
Now that I'm primarily using Go, I almost always get my answers from godoc.org (i.e., the documentation of packages), from source code, from the specification, and from trying things on playground. I don't remember using stackoverflow for Go programming questions in years, if ever.
I wonder if that's a property of Go language (great docusmentation, easily readable source, referenceable spec and viability of answering questions via playground experiments) that cause this, and if it applies to other people too.