I know this article is old, but I have often returned to thinking about how it is both entirely true, and total crap, depending on your perspective. :)
It is true that each bespoke app structure by each master Go developer will differ from another, especially based on the domain, size and complexity.
The Go team could definitely have provided some more official guidance on what they thought might be a reasonable starting structure for a particular popular app type. It didn’t need to be perfect for all purposes for all time, and they didn’t need to commit to enshrining it as an eternal example. They just didn’t have the appetite for engaging enough with the community to provide that, and justified it by being too “pragmatic”.
For instance, if you compare Mat Ryer’s various articles over the years there is a clear improvement (I only remember two them right now):
However, if you picked any one of them, and mandated your organization follow that initial template for any web applications it would still be entirely tolerable. Similar structural guidelines
“A poem is never finished only abandoned” said by Paul Valery
The Go team could have proposed something halfway reasonable for a starting web app, and it would have been helpful.
This seems like the author should use an opinionated framework and be done with it.
I know this article is old, but I have often returned to thinking about how it is both entirely true, and total crap, depending on your perspective. :)
It is true that each bespoke app structure by each master Go developer will differ from another, especially based on the domain, size and complexity.
The Go team could definitely have provided some more official guidance on what they thought might be a reasonable starting structure for a particular popular app type. It didn’t need to be perfect for all purposes for all time, and they didn’t need to commit to enshrining it as an eternal example. They just didn’t have the appetite for engaging enough with the community to provide that, and justified it by being too “pragmatic”.
For instance, if you compare Mat Ryer’s various articles over the years there is a clear improvement (I only remember two them right now):
However, if you picked any one of them, and mandated your organization follow that initial template for any web applications it would still be entirely tolerable. Similar structural guidelines
“A poem is never finished only abandoned” said by Paul Valery
The Go team could have proposed something halfway reasonable for a starting web app, and it would have been helpful.