Program your next server in Go

Re:Program your next server in Go by dalailambda on Tuesday June 07, 2016 @06:43PM (#11858596)

That's interesting. The cgo overhead was the only thing holding me back from considering it for games, since I didn't want to write a lot of C wrappers around the C libraries I want to use just to have them be more efficient, which is a shame, since Go is pretty nice, barring the C interop in some cases.

[ Parent | on HN ]

Re:Program your next server in Go by pjmlp on Wednesday June 08, 2016 @05:18AM (#11860985)

When I used to frequent gonuts, I raised the issue why they didn't went the FFI way as D, Rust, .NET, Delphi, FreePascal do, but sadly they rather use cgo as solution.

[ Parent | on HN ]

Re:Program your next server in Go by dalailambda on Wednesday June 08, 2016 @05:27AM (#11861024)

I'm pretty sure the problem is Go's use of segmented stacks and runtime, which makes it hard to properly interface with C efficiently.

[ Parent | on HN ]

Re:Program your next server in Go by pjmlp on Wednesday June 08, 2016 @06:01AM (#11861148)

Sure, but the compiler could generate that FFI code, why the need to rely on an external tool (cgo) and a C compiler?

[ Parent | on HN ]