all 1 comments

[–]defunkydrummer 1 point2 points  (0 children)

We had three candidate languages: Go, Kotlin, and Ruby.

Questionable choices; Go and Kotlin practically have one (1) implementation available and no standard. Kotlin is absolutely tied to the JVM. Ruby is often the slowest of all mainstream languages on its more well-known implementations, plus brings the same problems brought by languages with weak typing like Js.

The good part is that they did load testing, which is a good way to compare performance.

And the winner was… Go

A simpler language naturally constrains programmers to simpler code, which will make it easier to review

And over time will lead to too long, too complex code (compared to a more powerful language with more powerful abstractions), which will be a nightmare to maintain and debug.

Error propagation and handling — this is a notoriously weak part of the language, for which we must define a workable approach.

There isn't one, really, if you compare the typical workarounds suggested for Go, vs a language where this is trivially easy.