Hacker News new | past | comments | ask | show | jobs | submit login

If you want to render HTML, there's a lot of security features that you won't get with micro-frameworks. And even Beego and Revel have a lot to do to catch up with Rails and Django. So for this type of apps, I would stay with Rails or Django for now (depending on your preferences).

If you make REST APIs, then you can use a micro-framework because there will be less boilerplate to get to what you want. Goji and Gin offer great performances compared to Gorilla, Martini and the others.

I see a lot of companies using Rails or Django for their main app and Go for their background processes. I think this approach is a good first step to get better performances and knowledge of Go, keeping the productivity of these frameworks to render HTML apps.

Yes, I also think, if you're the kind of developer who wants a framework: Rails is probably an objectively better choice. My default "stack" is Rails front-end and Golang for JSON RPC stuff on the backend. Golang is nowhere close to Rails in terms of flexibly converting an SQL database to HTML.

My experience of building complex web stuff in Golang is very similar to my experience of doing the same with Sinatra: you inevitably realize about 1/3rd of the way in that you're really just building an underspecified, undertested version of Rails itself.

I have been long time Django/Flask users, and undoubtedly a good web frameworks give you some structures, security and impose good practices to new programmers, that's what I'm trying to find out. I'm not very aware of how advanced Go Framework are, but if there is something that could replace nicely my current Python web stack, I would be happy to give it a go.

You may not see this now, but does building a(n) SPA change your thinking on this at all?

(Assuming you build those, and I'm not suggesting that it would--more looking for additional viewpoints.)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact