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 548536
To read all comments associated with this story, please click here.
RE[7]: C -> Go
by Valhalla on Sat 12th Jan 2013 23:30 UTC in reply to "RE[6]: C -> Go"
Member since:

Furthermore, Go tip (1.1 in dev) has many many more optimizations than Go 1.0.3 and the compiler is 30% faster yet....

Sounds great, but it most likely means that the original compiler had lots of untapped speed improvements prior to this upcoming version. Implementing optimizations to be applied during code generation will slow the compiling down.

Oh, and both the Go compiler and the Go runtime are written in, you guessed it, C ;)

1. Your link does not include Go in the comparison.

Yes it does, it's two steps behind Java 7.

Your link is only considering execution time

That is how you measure language performance. Memory usage and code size are other metrics.

The is important because although Go is a little slower than Java (which is actually one of the fastest languages, BUT Java uses MUCH more memory

I actually don't think that matters much when it comes to the areas where Go and Java are likely to be deployed (which are unlikely memory constrained areas), obviously it's not a bad trait to use less memory though.

Still I think Go has every chance of eventually beating Java in raw performance, currently Java has what is probably the best in class garbage collector, Go's garbage collector is (as of 1.03 atleast) likely far behind.

Also in overall compiler optimizations the Go compiler sometimes loses out heavily to Gccgo on the exact same code, indicating that there is still alot of room for improvements to be made.

Again, I mean modern C as in C the general purpose language of the 1970/80s, not C is the systems programing language of today.

Well if you had framed it as such then I would have had no problem with your claim, although I would still find it odd to compare Go with C's much more widespread usage in the 70/80's as opposed to the areas it mainly occupies today.

...I was responding to someone who was comparing Go and D...

Ah, my bad, sorry.

Reply Parent Score: 2