After reading the thread I can kind of see why both sides have a good argument.
The provider of the repo seems to have created this as an opinionated way to lay out a Golang project, so that if you're new to golang you can skip some yakshaving over how to set up your directories.
Russ's issue seems to be that this is describing itself as _the standard way to lay out a Golang project_, which it shouldn't.
Most of the commenters seem to think changing the name would resolve this issue, and I'm inclined to agree. Opinionated frameworks aren't really a new thing, and while this isn't a framework per se, it's definitely opinionated.
2 comments
[ 2.7 ms ] story [ 19.8 ms ] threadThe provider of the repo seems to have created this as an opinionated way to lay out a Golang project, so that if you're new to golang you can skip some yakshaving over how to set up your directories.
Russ's issue seems to be that this is describing itself as _the standard way to lay out a Golang project_, which it shouldn't.
Most of the commenters seem to think changing the name would resolve this issue, and I'm inclined to agree. Opinionated frameworks aren't really a new thing, and while this isn't a framework per se, it's definitely opinionated.
This post and the related issue should be spead widely under the go community, so that at least everyone is aware of that.
Thank you for sharing.