The author of that article is overly focused on the Linux (or similar) deployment model, which most definitely does not cover all uses of SQLite. The argument against 2) also depends on a feature available in specific versions of specific compilers, which again, a piece of software that supports as many use cases as SQLite can’t depend on.
Even in that model, I’ve long found that the arguments against 1) are weak in practice (especially with a well-designed and maintained lib like SQLite) versus the additional complexity added by depending on dynamically linked libraries.
Even in that model, I’ve long found that the arguments against 1) are weak in practice (especially with a well-designed and maintained lib like SQLite) versus the additional complexity added by depending on dynamically linked libraries.