In my opinion, Go is great to make REST APIs, but for full-fledged frameworks (with server-generated HTML views) Rails will always be light years ahead for the developer productivity and happiness. That's why the article focus on a web framework to make REST APIs.
That is why Go frameworks need to be made though, the process of evolution will produce varying and improved frameworks. Flotilla(https://github.com/thrisp/flotilla/tree/develop) was started bring something Flask-like to the workflow at Thrisp. Its not rails and intended to be a micro framework, but aims for full-fledged.
Comments
The question is: Should you build a web framework in Go?
In my opinion, Go is great to make REST APIs, but for full-fledged frameworks (with server-generated HTML views) Rails will always be light years ahead for the developer productivity and happiness. That's why the article focus on a web framework to make REST APIs.
That is why Go frameworks need to be made though, the process of evolution will produce varying and improved frameworks. Flotilla(https://github.com/thrisp/flotilla/tree/develop) was started bring something Flask-like to the workflow at Thrisp. Its not rails and intended to be a micro framework, but aims for full-fledged.