Yeah definitely, starting the project in 2007 to releasing publicly in November 2009 is very fast. Then reaching a very stable 1.0 in 2012 is also fast. That'

Yeah definitely, starting the project in 2007 to releasing publicly in November 2009 is very fast. Then reaching a very stable 1.0 in 2012 is also fast. That's only possibly by reducing scope. I don't think more people help, because you can't really divide and conquer language design. (As far as I understand, the early project was something like "take Ken Thompson's C compilers and add goroutines, garbage collection, slices, and interfaces") I don't use Go regularly, but I've also had some very good experiences with it lately. They have kept the tools simple and predictable. Getting started is a breeze. The MIPS support worked surprisingly well, e.g. on a machine with 64 MB of RAM. I've had and still have a lot of gripes about (mainly being a sort of closed ecosystem), but you can't deny that it works well, and is a big achievement.