I don't have a personal opinion but I have seen similar situations on this list where one person wants to use an mvc project structure, and others suggest grouping them by types instead..
ie
user/
view.go
db. go
article/
view.go
db.go
I assume it is for the purpose of not having to jump between different packages to manage a single entity. But rather, keeping it all together.
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.