Re: [go-nuts] Arguments for writing fast, high-load servers in Go instead of Scala?

You may have come across this already, but here is another example of a team moving from Scala to Go https://movio.co/blog/migrate-Scala-to-Go/ Though not a move from Scala, Uber has also published some articles on how they've built high-speed services with Go.

Re: [go-nuts] Arguments for writing fast, high-load servers in Go instead of Scala?

On Fri, 17 Feb 2017 22:55:37 -0800 (PST) Will Faught wrote: > I want to make the case to a software architect where I work that we > should write some fast, high-load servers we need in Go rather than > Scala. What pragmatic arguments should I use? I do not do Scala but

Re: [go-nuts] Arguments for writing fast, high-load servers in Go instead of Scala?

The cognitive difference is huge in Go's favor. Aside from that the new impressive gc results built for low latency can be a good argument. We have deployed a number of services in Go over the past months and are very happy with the performance. We used to do all these in Java but Go is easier to

[go-nuts] Arguments for writing fast, high-load servers in Go instead of Scala?

I want to make the case to a software architect where I work that we should write some fast, high-load servers we need in Go rather than Scala. What pragmatic arguments should I use? Note that the architect isn't against ever using Go; the question is whether to use Go now, for these servers