> It's a royal pain writing go that talks to C code, compared to say, lua or python
This is plain wrong, you can pretty much call C code directly, while in Python and the like you really have to write a wrapper.
Of course in Go you will write a wrapper anyway to give the library a more Go-like API, but I don't see how this could be any worse than in any other language.
> there just _isnt_ a way to make other languages pickup go libraries and run the symbols from them afaik...
To get non-Go code to call Go code is trickier (also Go really wants to run your main()), but can be done, and there are even libraries to write Python extensions in Go, see:
This is plain wrong, you can pretty much call C code directly, while in Python and the like you really have to write a wrapper.
Of course in Go you will write a wrapper anyway to give the library a more Go-like API, but I don't see how this could be any worse than in any other language.
> there just _isnt_ a way to make other languages pickup go libraries and run the symbols from them afaik...
To get non-Go code to call Go code is trickier (also Go really wants to run your main()), but can be done, and there are even libraries to write Python extensions in Go, see:
http://gopy.qur.me/extensions/