Linked by MOS6510 on Thu 10th Jan 2013 23:25 UTC
General Development "For years I've tried my damnedest to get away from C. Too simple, too many details to manage, too old and crufty, too low level. I've had intense and torrid love affairs with Java, C++, and Erlang. I've built things I'm proud of with all of them, and yet each has broken my heart. They've made promises they couldn't keep, created cultures that focus on the wrong things, and made devastating tradeoffs that eventually make you suffer painfully. And I keep crawling back to C."
Permalink for comment 548613
To read all comments associated with this story, please click here.
RE[10]: C -> Go
by voidlogic on Sun 13th Jan 2013 16:25 UTC in reply to "RE[9]: C -> Go"
Member since:

Go 1.1 still slated for Q1 I hope?

Nope, I was hoping it would be that soon as well.

Here is a burn down graph, my understanding is when the blue line hits bottom 1.1 will be ready for release:

In the meantime you can always grab a snapshot of Go tip. A couple of the go core devs I talked to feel that for performance intensive uses this is the way to go. You can use the google issue tracker to make sure you don't care about any issues in a particular snapshot (many are feature enchantments, etc)

Reply Parent Score: 2