Golang

2217 readers

1 users here now

This is a community dedicated to the go programming language.

Useful Links:

Rules:

Posts must be relevant to Go
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 1 year ago

MODERATORS

Ategon

RandomDevOpsDude

austin

GitHub - golang-standards/project-layout: Standard Go Project Layout (github.com)

submitted 1 year ago by lysdexic to c/golang

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] lysdexic 1 points 1 year ago (1 children)

Yeah, there is no standard.

If you read the README.md file, you'll stumble onto the next paragraph right at its start.

This is a basic layout for Go application projects. It's not an official standard defined by the core Go dev team; however, it is a set of common historical and emerging project layout patterns in the Go ecosystem. (...)

I don’t like this repo and I’ve been recommending people avoid it for years.

Unless you have a better reference that you can provide in place of this one, I don't think you're doing anyone any good. People use these documents for guidance, and no guidance at all is clearly not a better alternative to a concrete example whose worst traits is not fitting someone's vague, subjective opinion.

[–] [email protected] 0 points 1 year ago

If you read the README.md file, you’ll stumble onto the next paragraph right at its start.

No need to read anything pass the project title, it says "golang-standards". If it not standards, maybe change the project title ?

Unless you have a better reference that you can provide in place of this one, I don’t think you’re doing anyone any good.

I gave two examples in my initial comment. I can provide more, if you want.