This is probably a good thing in many respects because Go doesn't have the baggage from yore, and it was created by some pretty smart and capable people.
As was Javascript plus Node.js two years ago, Ruby and RoR five years ago, etc.
You'd think that more reasons are required than 'it is new, doesn't have baggage in was created by smart people'.
Re:Go After 2 Years in Production
by kintamanimatt on Tuesday August 27, 2013 @04:07PM
(#6285927)
Go isn't a framework. NodeJS is a framework, as is Rails. JavaScript and Ruby are very old languages, both laden with baggage.
Re:Go After 2 Years in Production
by ricardobeat on Tuesday August 27, 2013 @10:24PM
(#6287658)
node.js is not a framework, it's a platform written in c++ and js.
Re:Go After 2 Years in Production
by kintamanimatt on Tuesday August 27, 2013 @11:24PM
(#6287865)
Yeah, you're right. Thanks for pointing that out.
Now would be a good time. No language, runtime, compiler, library, or framework is ever going to be perfect, but now is a great time to dive in.
> It still seems bleeding edge
This is probably a good thing in many respects because Go doesn't have the baggage from yore, and it was created by some pretty smart and capable people.
> but the language seems to have developed far faster than Python did over the last decade or so
Language designers are getting better at marketing. No language succeeds without fantastic marketing.