Go vs. Scala for real-time web applications

Question

I am writing a webapp that uses websockets to update positions on a Google map and to exchange messages with drivers in real time. I played with Node.js as well as Tornado, but I came to the conclusion that I would prefer static typing for this project.

Two excellent options seem to be Scala and Go, but it's hard for me to resolve these two issues. I mainly programmed in C / C ++ / C # / Python and had very little Java experience.

So how are these two comparisons? What would you learn next? I know that this is subjective, but I kind of looked for some battle stories. Also, what about the ecosystem? From what I can say, Scala inherits the Java ecosystem, but what about Go?

Answer 1

The downside of Go is immature, with very little experience in the real world.

The downside of Scala is that you must be familiar with the eco system for Java to make good use of Scala. You probably can't write everything in Scala. In addition, some may find the learning curve for Scala above.

Both support websockets (Scala via Lift, for example, and Go in the standard library).

I think Go will be more convenient for you, as it is more similar to Python than Scala.