[sshillo]

This is just another generic Go vs Node post. Do we really need another post telling us about Go's concurrency/built-in features/compile benefits.

This post sadly doesn't really go into much details that bowery.io is trying to solve, how Go fits that and why Node was so bad.

A basic crud webapp would probably be better suited towards node and it's larger list of libraries supporting that kind of stuff.

On the other hand, building you own messaging queue or doing heavy mathematical processing might be better suited for Go.

[falcolas]

Fwiw, I have been doing a lot of crud work in Gonthe past few months, and haven't found it particularly burdensome. I have to write my own SQL and map it back to structs, but I consider that a good thing. I might have to write about some lessons learned.

[kochthesecond]

Please do. I come from java, and am currently finding Go a bit cumbersome to work with. No Exceptions, lots of nil checks and a poorer ide makes it quite a bit of work. I also find testing a bit harder to do, but it's probably because I'm in a javian mindset.

[collyw]

Do you mind me asking why you chose Go? It sounds like the problems you have would all be solved by using a traditional language with a mature framework or ORM.

[je42]

Actually, I would like to see a case by case comparison why / how go's concurrency primitives are nicer/better than something equivalent in node.js/javascript.

[muraiki]

Not exactly what you're looking for, but it might help: http://notes.ericjiang.com/posts/791