Don't forget os/exec. If the performance overhead of invoking an
external process is acceptable, a mature application that's been around
for 10-20 years beats the one we just wrote last week. There are plenty
of such applications written in C/C++ in NIX world.
A lot of people have this funny notion of proper (using bindings) vs
improper (calling external command) way to use C/C++ from Go. If using
os/exec helps accomplish our goals within our constraints and it saves
us days or weeks of development and debugging, why not? I don't see
improper, just tradeoffs.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
