Since it didn't blow away "all" of the competition, this reader is curious about which other stacks held their ground.
This reader is also curious as to why Erlang wasn't in the competition, since Erlang meets all of the stated requirements (same programming language for backend and frontend systems, fast HTML templating system, fast start-up, modular recompilation, lots of connections on one machine, language tools for handling application-level concurrency, good performance, robust RPC layer to talk between tiers, lots of libraries, and open source). I'm guessing there was an unstated requirement along the lines of "syntax is not weird".
We'd love to experiment with Erlang at some point, at the very least to write an Erlang StatHat library.
(*Go's net package links against libc to get around domain resolution issues on various broken systems. This can be disabled if you want a truly standalone binary.)
deployment story for Erlang is not as simplistic as in Go, but it allows much more, including deploying and running several versions simultaneously, hot patching or live profiling. The philosophy of Erlang/OTP is drastically different from Go/Google production, so it's not easy to have a direct comparison.
Although Go is a young language, it has a lot of system
packages and a growing number of user-contributed
packages. With only a few exceptions, we have found Go
packages for everything we have needed.
Basically what I was referring to as missing were the Amazon SES package and braintree. We haven't released the package for braintree yet, but we will.
The built-in RPC is nice, but it seems like one would still want to use something like Thrift -- I assume that non-Go servers cannot talk Go RPC
He says it would be impractical for other browser vendors to keep up with the sprawling mess of APIs required by NaCl known as Pepper. Also Google's behavior around it's open source but not open standard tech like NaCl and Dart leaves a bad taste.
and i hope Google is listening. i mentioned in many comments before, i just see it there, unlike Dart.
PS: I presume the graph drawing library is written in-house, what did you use as the building blocks for it (both for design and implementation) ?
And, yes, the chart drawing library was written by us. It uses cairo for drawing primitives.
I wanted to use the experimental support for GO in google app engine but it seems fairly limited...at least for the time being.