To me having packages in an application is already a code smell, my
requirement is each non-main package should provide very specific
functionality that could be shared between applications.
I remember the Quake source code having most everything in one directory of
C files, and I think Go
is there a page such as "https://github.com/yksz/go-design-patterns; I can
refer to for golang design-patterns? I wish there were some official ones,
which can help language newbies and give them confidence that what they are
doing is the "right way". I understand it depends on the problem but
>
> I've been reading the other day: "having a model package, is considered a
> code smell, in Go".
>
> 1 - Why?
>
Assuming you are following the Model-View-Controller you will have to
export your full data model in model, so that controller and view can have
access to it. But then every
