Which version of Python (multiprocessing)?

Actually, they certainly can write compilers. But if the language is in its infancy, and likely to change often, it's certainly easier to change the C-generator than the machine-language-generator.
Right. Well put.

Sorry, perhaps my phrasing is incorrect there. What I meant was "as C does by default" - one assumes that for many things, C outputs the most optimal assembly possible so there would be no reason to re-write it.

Also, the idea that Google are employing incompetent developers to work on their language is just plain silly. Which explanation seems more feasible, you not understanding why they are doing it this way, or Google being utterly incompetent?
I didn't mean to imply that the designers of Go aren't competent, just that they are not compiler writers. They are high level programmers, who want to make writing high level programs easier.

Eventually, there will likely eventually be a Go compiler team that writes a compiler that directly compiles Go.

You are wrong. The C compiler itself optimizes; therefore, it is done NATIVELY.
What are you trying to say here?
 
Eventually, there will likely eventually be a Go compiler team that writes a compiler that directly compiles Go.

You'll be happy to hear that the speed of Go is now between two and ten times faster that at release. Oh, and to the people here who wanted a Windows port: They're working on that, too.

http://blog.golang.org/2010/03/go-whats-new-in-march-2010.html

What it needs next is a GUI. I can't really stand Objective-C -- too close to C -- but the GUI combined with Interface Builder and Xcode is really, really nice.
 
Back
Top Bottom