3 ms·

I think it's important to note that this is a very opinionated way to set up Golang projects. It relies on a lot of tooling not explained in the post plus uses

I think it's important to note that this is a very opinionated way to set up Golang projects. It relies on a lot of tooling not explained in the post plus uses some processes that may or may not be standard (eg the version is one of many ways to do it). In future posts you might want to break down why you do things the way you do and explain why you chose those solutions over others. For those interested in skipping initial page (which seems to be insanely slow), just check out the boilerplate repo: https://github.com/MartinHeinz/go-project-blueprint https://github.com/MartinHeinz/go-project-blueprint

MartinHeinz 7y ago
You are right, this is quite opinionated solution, as everybody has their preferred ways of coding. The fact that not everything is explained in this post is because there are 4 parts, which are all linked at the top of README in the repo you linked. The pages loads quite slow indeed, that's because of the traffic coming in right now... The 1GB RAM VM is having hard time serving all the requests...
- ben0x539 7y ago
  Do you think it might be worth it to prod a moderator to change the URL of this submission to https://towardsdatascience.com/ultimate-setup-for-your-next-golang-project-1cc989ad2a96 https://towardsdatascience.com/ultimate-setup-for-your-next-...?
kerng 7y ago
Go with all its intrinsic conventions is very opinionated, so its natural way of arguing about Golang.