On Mon, Oct 24, 2016 at 2:51 AM Carlos Ferreira <carlosmf...@gmail.com> wrote:
> > Using binds is a more efficient and direct approach. Also, why calling an > external command when you can just load a shared library? It never made any > sense to me... > One argument for calling externally is that it provides OS isolation for your external program. So if the program has an error, it can be handled without it destroying your own application. Such isolation barriers can do wonders for the correct operation of large-scale systems where you have no hope of removing every small error that are present in systems you rely on. In contrast, a shared library can wreak havoc in your own memory space. There is added efficiency, but that comes at a trade-off. Many problems doesn't need that added efficiency, but needs the resilience against errors. -- 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.
