[go-nuts] Re: The next layer of abstraction for Go development?

2020-06-15 Thread Anderson Queiroz
My opinion is that one of the reasons other languages need a framework is that the standard library is too hard to work with. So the frameworks take some of these burden and also take a lot of decisions for the you. In Go the standard library is powerful and simple enough to us to build the

[go-nuts] Re: The next layer of abstraction for Go development?

2020-06-14 Thread Saied Seghatoleslami
As evidence for not needing the next layer of abstraction, I offer Django class-based-views. The go approach is much more understandable and easier to follow. On Saturday, June 13, 2020 at 4:11:59 PM UTC-4, Asim Aslam wrote: > > Might not be the right place for this discussion but also useful

[go-nuts] Re: The next layer of abstraction for Go development?

2020-06-14 Thread David Skinner
I am very very old, and very old school, so I always start with UMLs and ERDs and design my apps long before I do any coding. These flowcharts are visual representations that are concise and easy to understand and they are saved as XML which can be parsed by a Go program controlled by +generate