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 both develop and deploy as well as fast so the choice is easy going forward. The only argument imho could be if you have some library in Scala/Java that implements something really specific with high quality then it makes sense I guess to reuse that. On Sat, Feb 18, 2017, 07:55 Will Faught <will.fau...@gmail.com> 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? > > 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. > -- 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.
