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 in particular. Not much detail has 
been hashed out yet about them, aside from general speed and load 
requirements.

As a general example of a pragmatic reason one might choose Go over Scala, 
the architect said Scala would be bad for making a standalone program that 
checks gRPC health endpoints because the binary would be large and the 
start-up time would be long.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to