3 ms·
This article doesn't make a good case against static linking, and the author doesn't seem to understand what vendoring is either: > Bundling (often called vend
by IshKebab 6y ago
This article doesn't make a good case against static linking, and the author doesn't seem to understand what vendoring is either:
> Bundling (often called vendoring in newspeak) means including the dependencies of your program along with it.
No, vendoring means including a copy of the source code of dependencies in your repo. You can bundle dependencies without vendoring them.
The only argument presented against static linking is that when a library is updated rebuilding dependants takes longer (and people will have to download bigger updates but I doubt many people care about that).
That may be true, but is it really that big of an issue? I somewhat doubt it (for sane distros that don't make users build everything from source themselves anyway).
The author clearly doesn't like how people do development these days but hasn't stopped to think why they do it like that.
- UncleEntity 6y ago> The only argument presented against static linking is that when a library is updated rebuilding dependants takes longer (and people will have to download bigger updates but I doubt many people care about that). Not really, the argument is that instead of rebuilding one library you now have to rebuild hundreds of applications to see the benefits for whatever the library update was for...assuming upstream even cares enough to bump the version number for the who knows how many libs they are vendoring because they have other stuff to do which is way more important.
- IshKebab 6y agoRight but that can be done automatically for static linking just as easily as it can for dynamic linking. So the only difference is time and downloads. I think you're conflating static linking and bundling and vendoring a bit, like the author is. They're all different things.