Spyke
lemmy.ca

Yeah, there is no standard.

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

If you need examples, checkout the golang source code or kubernetes repo.

1
lysdexicreply
programming.dev

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.

0

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.

0
lemmy.world

Why do people insist on some “standard” here?

Smacks of junior developer.

1

Pretty much. Once you get into the suck, you very quickly learn there isn't a standard beyond that which the project/org dictates.

1

You reached the end

GitHub - golang-standards/project-layout: Standard Go Project Layout | Spyke