On 24/10/16 11:50, Carlos Ferreira wrote:
It's improper because it is not the correct way of doing things. Calling external commands usually require calling the terminal and all of the overhead that it requires.
Agreed. That's why I did not say that it didn't come with any overhead.
Using binds is a more efficient and direct approach. Also, why calling
Every benefit comes with a cost. Raw performance overhead is one such cost. There are others. If such cost is the only thing that matters, no Go developer would be using Postgresql (whose call from Go has far more overhead).
an external command when you can just load a shared library? It never made any sense to me...
I use shared libraries far more frequently than I use os/exec.
I have my share of Python development and every time I need to implement a feature that requires an extra kick (performance), I do it using binds and by implementing my own Python Module.
Love python. You don't write an external module every single time do you? :)
Laziness today is a problem tomorrow.
Laziness is the mother of many inventions :D -- 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.
