I'm usually the last person to jump to the defense of anything golang related... but people seem to be raising eyebrows about the nodejs dependency. Assuming they're using it for asset compilation etc I really don't see the problem. There's no reason to keep rewriting that stuff in every language.
NodeJS is not a horrible dependency and it's not required when creating a new project. It's not like everyone doesn't already have Node or NVM installed for some other project.<p>How else is the framework going to handle/bundle these two parts together? There is so much code already out there that works for developing rich frontends that it seems silly for a "framework" that is trying to handle everything for you wouldn't handle that.
Also checkout go buffalo <a href="http://gobuffalo.io/" rel="nofollow">http://gobuffalo.io/</a> the claims are nearly the same "Rails for go" .<p>Too bad they didnt collaborate to make a single project better.