1. The 32 bit memleak is indeed a prioirity and the Go team has made definitive statements about dealing within coming couple weeks. 2. Most of the team is a b

1. The 32 bit memleak is indeed a prioirity and the Go team has made definitive statements about dealing within coming couple weeks. 2. Most of the team is a bit young and cheeky but they do mean business and actually engage the public very patiently about modifications/improvements etc in their mailing list. The dismissive attitude is usually them trying to stick to their core goals of making go an expressive, orthognal and highly readable language. Usually they have good enough reasons for picking a choice. I would seriously recommend you to "not browse through" some source code but rather "play" with it. It really does feel different. Its like the feel of a quick dynamic language but on a more type safe static language. Its kindof fun at the least. Not the mention their CSR inspired concurrency approach. Its really interesting. Give it a shot, what you got to lose?