3 ms·

I finally came up with an analogy for Go to use whenever talking with someone on the fence of trying it: "Golang is to dynamic web development what Laravel (an

I finally came up with an analogy for Go to use whenever talking with someone on the fence of trying it: "Golang is to dynamic web development what Laravel (and similar) are to Php". My feelings are that if you're amazing at C++ or Java and you need to write a highly performant and scalable service you are probably best to stick with that. But if you're like most developers and not great at C++ or Java (and perhaps never will be) Golang is a superb middle ground that makes highly performant and scalable services more accessible to developers trying to tackle those problems for perhaps the first time. I'd be interested to hear what the community thinks of the analogy.

languagewars 10y ago
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.