News for hackers. Stuff that matters.
Re:Beating C with 70 lines of Go by 0xdead on Wednesday November 20, 2019 @03:31PM (#21588152)
> Go can be a viable alternative to C as a systems programming language

Stop this nonsense please. This does not show anything even remotely close to systems programming capability of Go. Write a device driver in Go that performs without lagging, benchmark it and then come back.

Re:Beating C with 70 lines of Go by pjmlp on Wednesday November 20, 2019 @05:43PM (#21589434)
Yep, real nonsense, that is why this stuff exists:

- gVisor hypervisor on Google Cloud and Linux sandbox on Chromebooks

- Android GPGPU debugger

- Fuchsia TCP/IP stack and volume management

- Baremetal TinyGo on Arduino Nano33 IoT, Adafruit Circuit Playground Express, BBC micro:bit among many others

- Coreboot firmware

- Biscuit POSIX like OS

Re:Beating C with 70 lines of Go by weberc2 on Wednesday November 20, 2019 @04:10PM (#21588555)
"systems programming" is not well defined. While you and I probably prefer a similar definition, comments that criticize TFA for not using our preferred definition are really boring. Let's just say that Go is a fine language for `wc` (and not a very good language for device drivers) and move on.
Re:Beating C with 70 lines of Go by xpe on Wednesday November 20, 2019 @04:38PM (#21588833)
This Wikipedia article suggests that Go is not regarded as a systems programming language:

https://en.wikipedia.org/wiki/System_programming_language#Ma...

Re:Beating C with 70 lines of Go by grumpydba on Wednesday November 20, 2019 @04:25PM (#21588686)
https://news.ycombinator.com/item?id=18399389.

It's been done. Performs well.

Re:Beating C with 70 lines of Go by rowanG077 on Wednesday November 20, 2019 @05:21PM (#21589229)
They quite literally were forced to use C for some parts because Go is not a systems programming language. They write this in the article.
Re:Beating C with 70 lines of Go by grumpydba on Thursday November 21, 2019 @04:31AM (#21592596)
> As we wanted to keep unsafe code to a minimum, we instead chose to employ the C code from the original driver as an opportunity to present cgo.

It's not for performance reasons. I think you misread. Also the driver is pure go now:

https://github.com/ixy-languages/ixy.go

Re:Beating C with 70 lines of Go by rowanG077 on Thursday November 21, 2019 @06:18AM (#21593085)
Systems language is not only about performance. Where did you get that?
Re:Beating C with 70 lines of Go by grumpydba on Friday November 22, 2019 @03:02AM (#21603734)
They never said that they had to use c because go is not a systems language, so your assertion looks wrong. They wanted to avoid using unsafe. In c everything is unsafe by the way, so it makes it less of a systems language?
Re:Beating C with 70 lines of Go by rowanG077 on Friday November 22, 2019 @05:05AM (#21604292)
No Go isn't a systems language because for one you don't have direct control over memory if you need it. For instance Go doesn't even have the volatile keyword which is essential in many cases when interfacing with hardware. The paper you linked laments this as well.