Open Sourcing Our Go Libraries (2014)
Using Go (or Scala or Java or whatever) doesn't magically scale a large system.<p>Scaling problems in large systems are rarely solved at the micro level, i.e. you don't "scale" by simply gaining the ability to run more operations in a single thread. This is always the problem with "language X is more scalable than Y" debates. From my experience scale has little to do with language, everything to do with how you use it.<p>This post brings to mind another written by Alex Payne a few years back about scaling in the large vs. scaling in the small:<p><a href="https://al3x.net/2010/07/27/node.html" rel="nofollow">https://al3x.net/2010/07/27/node.html</a><p>The danger with making hand-wavy claims with very few technical details is that it perpetuates the notion that there are certain magic bullets out there that will magically make your system "scale" if you use them. In the past few years we've seen quite a few large companies in SV and SF make the switch to some shiny new language (Scala, anyone?) only to find several million dollars and many months later that they're still having conversations about how to make stuff scale. Only now they're talking about making it happen in a language that is fairly new to their organization and with which they have only a few real experts.