As a C programmer I make a concious effort to ignore the possibility of using C for site specific code on the web, so I find C++ a stranger choice. For Java (or

As a C programmer I make a concious effort to ignore the possibility of using C for site specific code on the web, so I find C++ a stranger choice. For Java (or Scala), the problem is the baseline for running a VM. When I think of average Java webapp, I think of intranet apps doing nothing but needing 8GB of RAM. Java allows for good upward scalable design, but in average use it is like airlines buying fleets of spaceshuttles in case a new route is requested. I think go solves my issues with using C, but introduces two others.. No one writes stubs to interact with go, just C, so I am not writing a permanent "neutral" resource. Go has (had I should hope?) the crazy static linking thing. I reject the possibility of using a static copy of any common code. Everything that could conceivably have a security bug should be forceably swapped by a rude package manager, such that my program breaks before running indefinitely with a disclosed security bug.