zlacker

[parent] [thread] 2 comments
1. pjmlp+(OP)[view] [source] 2024-01-24 06:33:57
The whole "cgo is not Go" bashing is a kind of joke, maybe if Go 2 ever comes to light, one of the first breaking changes should be to remove cgo.

There, beautiful Go code from that point onwards.

replies(1): >>beautr+e7
◧
2. beautr+e7[view] [source] 2024-01-24 07:55:55
>>pjmlp+(OP)
Dear Lord, no! I depend on cgo for my game!

What's more, I have no complaints about cgo. It hasn't been a performance problem at all (my game runs smoothly at 240hz). And the interface for binding to C is quite simple and nice to work with (I made my own bindings to SDL2, OpenGL, and Steamworks).

Cgo did make cross-compiling trickier to set up, but I managed to do it with a fair amount of elbow grease (Windows and MacOS builds on my Linux desktop).

replies(1): >>pjmlp+ah
◧◩
3. pjmlp+ah[view] [source] [discussion] 2024-01-24 09:30:30
>>beautr+e7
That is my point with my sarcastic remark, cgo should be embraced for the workflows it offers, instead of the whole "cgo is not Go" drama.
[go to top]