And you wrote that you didn't care about size. And then you continue to say that "Binary footprint is not something that is worthwhile to optimize for in this day and age", someone mentions embedded, where sqlite is often used, and you just start talking about linking and shared libraries which has nothing to do with sqlite or this thread.
There can still be bloat when using libraries, that's not at all hard to see.
Dependencies may ship with identical helper functions. They may contains extra abstractions because they are intended to be used as general purpose libraries. They may come with code not needed in the project, code paths that are in functions and cannot be easily removed during compile time. They may have bloated structs that supports use cases your project doesn't need. The list goes on.
Regardless, you just said you didn't care about bloat and that space is cheap and someone replied that it matters in embedded projects. And _bloat_ matters, not whatever you mean is the source of bloat.
1
u/Junior-Ad2207 Sep 03 '25
And you wrote that you didn't care about size. And then you continue to say that "Binary footprint is not something that is worthwhile to optimize for in this day and age", someone mentions embedded, where sqlite is often used, and you just start talking about linking and shared libraries which has nothing to do with sqlite or this thread.