On: Four days of Go

[Xeoncross]

"Web Applications" are often made up of parts now. So while php/ruby/python are faster to develop for most things - writing the websocket handler or AJAX polling API in Go makes a LOT more sense given the performance of these crucial parts of the application.

I am currently using the massive PHP + Node.js ecosystem for most of the application and Go for the critical communication parts.

[jkarneges → Xeoncross]

I second this approach of mixing components. While I have not personally used Go, I have used Tornado and C++ to handle complex networking code, and I'd never use these as a complete substitute for "web application" development.

My current company's web API is built using Django, which may come as a surprise since we also do realtime stuff, but that's the benefit of mixing the best tools for each job.