|
|
|
|
|
|
by _ph_
1642 days ago
|
|
|
I didn't want to claim that you should use C libraries when you don't have to. But I knew the article, and it underestimates the value of being able to use libraries which are already there. Rewriting them is often not practical or even possible. |
|
|
For HN comment readers that skip citations (I'm not saying you did, just helping the conversation):
First paragraph
> cgo is an amazing technology which allows Go programs to interoperate with C libraries. It’s a tremendously useful feature without which Go would not be in the position it is today. cgo is key to ability to run Go programs on Android and iOS.
Last paragraph
> To be clear, I am not saying that you should not use cgo. But before you make that Faustian bargain, please consider carefully the qualities of Go that you’ll be giving up in return.
I don't see this as devaluing.