It seems a little unfair to ding Golang for not providing evidence of something Golang was designed to avoid. "Where's all the boilerplate? Where are all the 10 layers of XML mapping? What would an AbstractStrategyFactory even look like?"
Rest assured, if Go manages to become a success in the enterprise you will get them.
It happened to every language without exception.
But will it happen to one without exceptions, as well?? :)
Re:Brad Fitzpatrick on the future of Go
by placeybordeaux on Wednesday October 15, 2014 @10:24AM
(#8458543)
Panic/Recover will be used as expections.
If "enterprise applications" mean over-architectured monstrosities filled with boilerplate code, a hundred levels of indirection and horrible XML configuration files then thank god Go doesn't encourage that.
Most people simply don't have an understanding of enterprise applications. The majority of the apps are single codebase, Servlet/Spring type monstrosities. They are 10+ years old and have had hundreds of contract developers who come in, add a few new features and then go onto the next contract.
And my point is that I am yet to see what Go would be like in these situations.