3 ms·
> I would love to know when would be a good time to start using Go in serious production work Now would be a good time. No language, runtime, compiler, library
by kintamanimatt 13y ago
> I would love to know when would be a good time to start using Go in serious production work
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.
- gnur 13y agoExactly, there is never a better moment to start learning something new then now.
- danieldk 13y agoThis 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'.
- kintamanimatt 13y agoGo isn't a framework. NodeJS is a framework, as is Rails. JavaScript and Ruby are very old languages, both laden with baggage.
- ricardobeat 13y agonode.js is not a framework, it's a platform written in c++ and js.
- kintamanimatt 13y agoYeah, you're right. Thanks for pointing that out.