Linked by Thom Holwerda on Mon 11th Feb 2013 22:59 UTC
General Development "I feel like writing about the Go programming language (or 'Golang') today, so instead today's topic is computer stuff. For the record, the language I've programmed the most in has been Python, so that’s the perspective I'm analyzing it from." Some good and bad things about Go.
Thread beginning with comment 552211
To read all comments associated with this story, please click here.
A solution in search of a problem
by FunkyELF on Tue 12th Feb 2013 14:31 UTC
FunkyELF
Member since:
2006-07-26

It seemed that fast compilation times was a goal of the language. If it was a side effect, then great, but I think they were trying to address a problem that nobody really had.

I'm upset that Google abandoned the Unladen Swallow project to make Python faster and integrate LLVM. Had their new Go language targeted LLVM I'd be less upset.

Reply Score: 4

Valhalla Member since:
2006-01-24

It seemed that fast compilation times was a goal of the language. If it was a side effect, then great, but I think they were trying to address a problem that nobody really had.

Actually I recall the Go authors stating that indeed compilation speed was an issue for them in their large C++ projects at Google which made it a focus for Go.

Had their new Go language targeted LLVM I'd be less upset.

Ehh, why would it matter? Anyway, the Go devs looked at both GCC and LLVM as backends but found them both too large and slow and instead wrote the Go compiler from scratch.

There is GCCGo which I suppose is largely a stopgap solution to offer better optimization and support a larger range of architectures while the official toolchain matures.

Reply Parent Score: 2