Linked by MOS6510 on Thu 10th Jan 2013 23:25 UTC
"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."
Thread beginning with comment 548613
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2006-01-24
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)
Probably give it a shot again, last time I tried it (pre 1.03) there were some problems with some cgo bindings I used.
Still it's not as if I can't wait for the 1.1 release, as I said I'm not doing any production code in Go so performance isn't really an issue. Just trying to grok the language on my spare time, sofar so good
Member since:
2005-09-03
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: http://swtch.com/~rsc/go11.html#
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)