You started learning Go a month ago and, as a total beginner, you've written 1,000 lines of code per day in it? (20000 / (4 weeks * 5 days)). 125 lines per hour! This is a somewhat unbelievable figure.
I'm also skeptical about coming to decisions like this:
> And it's good enough in enough areas for me to set Go as the standard, de facto language at my company, unless there's a damn good reason to use another language.
...based on a single, one-month, one-man project. That's like deciding to only use a hammer to build everything from now on just because the hammer worked so great with a birdhouse.
I work 14 hours, workout for 2 hours, and sleep 6 hours a day, 7 days a week. This is my company and I'm bringing it into existence. Not to mention that LOC count includes testing which I write in standard TDD fashion. Furthermore, a number of prototypes were built in Ruby prior to working with Go. And the design for the core set of services was thoroughly planned and documented.
While I may be a total beginner in Go, I am absolutely not a junior software engineer. Go lends itself to being learned quickly.
No. It's not based on a single, one-month, one-man project. It's based upon a series of pain points I've felt over the years working in a number of different languages, on a number of different projects, with a number of different teams. Go solved enough of them to be worthwhile.
Your simile is flawed. It's like deciding to use one hammer to hammer all nails from now on until it breaks. I'm optimizing for aggregate throughput of a mid-sized team working on the problems we have over the course of 3 years. Go fits the bill for all the reasons I discussed above.
If you want to offer up a more detailed point-of-view, please do. That'd be much more appreciated than such a vapid, dismissive piece of criticism.
I'm also skeptical about coming to decisions like this:
> And it's good enough in enough areas for me to set Go as the standard, de facto language at my company, unless there's a damn good reason to use another language.
...based on a single, one-month, one-man project. That's like deciding to only use a hammer to build everything from now on just because the hammer worked so great with a birdhouse.