News for hackers. Stuff that matters.
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.