The Revel Web Framework for Go
Could someone explain what problem this solves? Go already has http, templates, and (duh) goroutines. What is Revel adding?<p>Sure, PHP programmers are accustomed to having their syntax errors detected by surprise at runtime. But aren't we choosing Go because it can detect those errors before we've deployed? [1]<p>In Java it may feel natural to take a simple task like dispatching a URL ("Routing"), and turn it into an elaborate overabstracted object architecture. But aren't we choosing Go to escape that nonsense? [2]<p>[1] <a href="http://robfig.github.io/revel/img/helpfulerror.png" rel="nofollow">http://robfig.github.io/revel/img/helpfulerror.png</a><p>[2] <a href="http://robfig.github.io/revel/manual/concepts.html" rel="nofollow">http://robfig.github.io/revel/manual/concepts.html</a><p>Am I missing something?<p>EDIT: I've seen lots of Go applications, and none of them have spent 8432579842375 hours developing scaffolding. Actually, they saved time not having to spray their logic across a zillion source files.