When I read the blog, the first thing I thought was "boy am I glad I don't use rails". I realize all frameworks and toolkits have issues, but Rails seems to be particularly bad.
I think the big take away here is the importance of apparently redundant sanity checks....
They all have issues - sure - but I've never encountered one so likely to break so spectacularly. Then again, it feels like ActiveRecord is a more complex beast than most others I've used.
I've mostly used Hibernate and NHibernate, and SQLAlchemy a few years ago.
I don't think that is fair; I did say "so much depends on what exactly you need."
Maybe you don't need to whole kitchen sink. Also its not as though there are not other Go libraries to get other functionality from such as DB/ORM functionality.
If people want something like Rails in Golang, it probably makes more sense to point them at Revel. Gorilla is more like Sinatra, for better or for worse.
Yeah, I don't think Gorilla or Revel are quite mature or stable enough at this point to consider as a Rails replacement. And I'm speaking as a (extremely minor) Revel contributor - it's still very young, early adopters only!
I've started a side-project using Go + Gorilla. It's actually very nice, but I don't think it's quite as productive for the early-stage as Rails is.
I can certainly recommend Django - I've been working with a large-ish Django codebase for 3 years and have yet to see a security vulnerability as bad as the ones Rails seems to have every month.
While fully realising that the language itself is pretty terrible, Java + Spring + JavaMail is a pretty good framework and as a bonus involves minimal XML these days.
I'm sure one of the alternative JVM languages would make this setup tolerable to work with, even pleasurable, but I don't know them.
I think the big take away here is the importance of apparently redundant sanity checks....