3 ms·
Pros: * single binary that you can scp (or use transfer.sh haha) into the production machine and run; no runtime environments, package installation etc. * two
by adtac 8y ago
Pros:
* single binary that you can scp (or use transfer.sh haha) into the production machine and run; no runtime environments, package installation etc.
* two different applications can depend on different versions of a library without any intermediate package manager or virtual environment
* guaranteed execution: related to the first point, but I see enough merit in this to make it a separate point
Cons:
* If there's a security issue in a commonly used library (database/sql, for example), you'll need to patch every application that uses it. With dynamic dependencies, you just patch the library.
- deathanatos 8y agoOne more con: shared libraries can be shared in memory; static binaries cannot.