Go vs. Scala for realtime webapps [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 11 years ago.

I'm writing a webapp that uses websockets for updating vehicle positions on a google map and for exchanging messages with drivers in realtime. I've been playing around with Node.js as well as Tornado, but I've come to the c开发者_运维知识库onclusion that I'd prefer static typing for this project after all.

Two excellent choices seem to be Scala and Go, but I'm having a hard time deciding between those two. I've been mostly been programming in C/C++/C#/Python and have very little Java experience.

So how do those two compare? What would you learn next? I know this is subjective, but I'm kind of looking for some battle stories here. Also, what about the ecosystem? From what I can tell, Scala inherits Java's ecosystem, but what about Go?

---

The down side of Go - immature, with very little real world experience.

The down side of Scala - you must be familiar with the Java eco system in order to utilize scala well. You probably can't write everything in Scala. Also, some might find the learning curve for Scala higher.

Both supports websockets (Scala through Lift for instance, and Go in the standard library).

I believe that you'll be more comfortable with Go, since it's more similar to Python than Scala.