News for hackers. Stuff that matters.
Re:A turning point for GNU libc by wglb on Tuesday April 03, 2012 @12:56PM (#3793744)
Originally they were targeting "systems programming", and, being roughly the contemporary of the most well-known go authors, "systems programming" used to mean compilers, assemblers, and the like. In this meaning, this would also include browsers, although Mozilla is going for Rust.

Today, "systems programming" is more taken to mean "kernel programming", and I don't get the sense that is what was meant by the senior authors of go.

Re:A turning point for GNU libc by acqq on Tuesday April 03, 2012 @06:48PM (#3795199)
I always believed "system programming" meant "programming operating system components or the whole operating system" and Wikipedia seems to agree:

http://en.wikipedia.org/wiki/System_programming

Last time I looked, inside of the Go libraries which had to do some tricky things there was some C code, meaning that even Go authors weren't able to write everything in Go. So Go can't be a substitute for C, and as long as most of the system programming is done in C, no go for Go.

Re:A turning point for GNU libc by 4ad on Tuesday April 03, 2012 @07:14PM (#3795288)
That's like saying C is not a system programming language because if you write a kernel you need to write parts of it in assembly, and you need to write parts of libc in assembly as well!

Parts of the runtime are written in C and assembly, but that's because there is power in breaking abstractions: http://research.swtch.com/goabstract

As it stands today, Go can be used to write operating systems. Yes, you will have assembly, yes you will likely also have C, so what?

Re:A turning point for GNU libc by wglb on Tuesday April 03, 2012 @07:40PM (#3795373)
That is what "system programming" means these days. It used to exclude operating system kernels, real-time components.

I suspect that it isn't so much that they aren't able to write everything in Go, but more that it isn't a priority for now. It wouldn't surprise me if Go wasn't eventually self-hosting.

Re:A turning point for GNU libc by rhizome on Tuesday April 03, 2012 @01:08PM (#3793803)
Originally they were targeting "systems programming"

Choose the greatest impediment and cite it as a primary goal.

Re:A turning point for GNU libc by wglb on Tuesday April 03, 2012 @03:42PM (#3794456)
I am not quite sure if I follow you. Are you saying that "systems programming" is the greatest impediment?
Re:A turning point for GNU libc by burgerbrain on Tuesday April 03, 2012 @04:26PM (#3794656)
Targeting systems programming is. The existing languages used there are rather firmly entrenched.
Re:A turning point for GNU libc by slowpoke on Wednesday April 04, 2012 @06:41AM (#3796942)
And that's a problem. If you want to do system programming, there's C. And that's pretty much it. I don't think this is a very favorable situation.
Re:A turning point for GNU libc by rhizome on Wednesday April 04, 2012 @11:51AM (#3798105)
Why not? It's the language that was used to write the OS, which is why Perl and shells still hold sway here as well.