Understand project structure of GO. Go Modules, GOPATH, efficent development environment... This repo contains lots of trash folder/file! Just trying to understand structure with trying lots of unnecessary things too
| https://www.digitalocean.com/community/tutorials/how-to-use-go-modules | 👉 Modules - How to use them | [module-str](simple-structrue/module-str/mymodule/) ✔️ |
| https://www.digitalocean.com/community/tutorials/how-to-write-packages-in-go | 👉 Packages - How to use them | [package-str](simple-structure/package-str/) ✔️ |
| https://github.com/golang-standards/project-layout | ⭐ Unoffical but ready-to-use go project structure | ✅ |
<br><ul><li> No, previously GOPATH was used but now Go Modules are using instead of that. Thanks to Go Modules, go.mod file handles all versions/modules/packages and there is no need for a virtual environment. But if you have to use a virtual environment because of another reason just have a look at <ahref="https://github.com/GetStream/vg">this</a> repo