HNHacker News
TopNewBestAskShowJobs

floops

32 karma · joined December 9, 2013

submissionscomments
floops··on Choosing Go to implement the new GOV.UK router
Or maybe you're trying to deal with a huge legacy content migration of several hundred different government agencies and want to deploy several times a day without waiting for 10 minutes for nginx to load 1MB of config each time?
floops··on Choosing Go to implement the new GOV.UK router
Dynamic route updating with nginx is not fun.
floops··on Choosing Go to implement the new GOV.UK router
A lot of the comments here seem to be missing something quite important: Scala and Go are not similar languages.

Scala is a large and complex language, encompassing multiple programming idioms. Teams programming Scala (as with C++ and many other "large" languages) often have difficulties nailing down what portion of the language they are going to use. "Java-without-semicolons" all the way through to idiomatic, functional Scala.

Go is a relatively small, simple language. You could easily learn Go's basic syntax and semantics in an afternoon or two. Simplicity and suitability for programmers is an explicit design goal.

Switching away from Scala due to lack of experience while simultaneously picking up Go is not as illogical as everyone seems to be implying.