The article does link to that blog post, and points out some problems with it.
I'm not a fan of this design either personally, in particular requiring a v2 suffix, I think it makes assumptions about versioning which don't withstand scrutiny, e.g. that major versions are always used for major breaking changes. In my experience they are more often used to indicate major feature releases.
I'd really rather go kept the culture of no breaking changes rather than explicitly encouraging them if you move past 1.x.
Really dislike the way this hides updates to modules, but I guess that's the price of stable imports
All informations about this here : https://blog.golang.org/v2-go-modules
However, In my opinion it's an unfamiliar and tedious design
The article does link to that blog post, and points out some problems with it.