[cjbprime]

> Could you clarify what you mean by "systems programming"? To me, that means working with embedded systems, which Go is certainly not appropriate for.

The blunt but approximately correct version is that embedded means that you're running on hardware that isn't powerful enough to run a Linux kernel.

Systems programming just means you're working below the application layer. So if you take your laptop and write a device driver, or work on filesystem or networking code, you're doing systems programming without doing embedded.

[waps]

Just curious : how does one run go without a linux kernel ? (without a kernel at all, please, I know about the freebsd port)

[cantankerous]

You'll probably be looking for a Go runtime that fills a kernel shaped hole. Without a kernel, where do all your syscalls go?

[waps]

Yes but the point of the parent poster was that go can work on minimal embedded systems, which to my knowledge it cannot, so I enquired.

[lmm]

No, the point of the parent poster was that "systems" is not the same as "embedded", and that while go may not work on the latter it can work on the former.