Go is such an easy language as it is, these kinds of frameworks just encourage amateur developers to skirt by with minimal understanding of what they're really doing. An MVC framework sounds like a great personal hacking project for fun, but I would beware of advertising anything like it for professional use.
What's so wrong with getting productive faster. Learning takes time. It is not very hard to write Go web apps with the standard library, but it may be more convenient to use a framework for the sake of time.
It is an assumption that amateurs will defer learning due to the framework. It also seems as though there is another assumption that all the people using this framework are somehow amateurs. It is convenient to be able to write a quick program using a framework and then being able to scale that project as it grows.
> with minimal understanding of what they're really doing
In my opinion, this is very dangerous. It is always better to understand the inner workings and then write an app, otherwise you just feel you have accomplished something when, in reality, it was just the framework you used and you didn't learn. I am saying this out of experience, when I used to use Django, I didn't understand the difference between GET vs POST. Still, I built a small note taking app, I didn't understand how cookies worked and until I wrote this: https://github.com/thewhitetulip/Tasks, I didn't know that the cookie details were read and sent to the sever in each request.
Frameworks are powerful in cases when you want new comers to get started quickly, but in my opinion that has to be after the new comers are familiar with webdev, so they know what the underlying tech are and how they work. Plus, frameworks need to be chosen with care, because you are basically bound to the framework you choose.
Personally, I like to write apps without a framework by using various toolkits, I never felt the necessity to use any framework, because they don't provide me with any distinct feature which I can't replicate with little additional code using the stdlib and supporting toolkits like gorilla.
From my experience building the Tasks application, I wrote an introductory e-book which teaches building apps with example, so no more magic! I didn't find a resource which taught how to write web apps using an example, thus wrote one.
the response struck a chord with me because a few years ago, I was just like the author suggested, someone who didn't know how to build a webapp and tried Django etc. Thus, I strongly that we need to understand the basics first.
I think most devs would have the flexibility of mind to adjust to whatever framework (or whatever ad-hoc, informally-specified implementation of half a framework) you use in-house. Many of the frameworks are not very different and lean heavily on the stdlib anyway, this is not rocket science, frameworks have different uses and strong points and the community does not have to be divided in religious war between different frameworks or framework advocates and the church of the one pure stdlib.
I am sorry, I still didn't get your concern. It is easy in my opinion to identify the person writing Go code. Look at their Github profile! (I am not a recruiter, so I don't know how effective that really is, but Github profile does reflect a person's contributions to FOSS and if the person is a FOSS contributors, look at their repos or their other PRs or their projects)
