undefined | Better HN

0 pointsflohofwoe2y ago0 comments

> None of this solves C's only REAL problem (in my opinion) which is the lack of dependency management.

I thought this too for a long time, but the more I'm exposed to languages with "proper" dependency management the more I appreciate the C way of just copying external library sources into the project (and I only consider libraries which make this easy, e.g. if they come with their own complex build system files they already lost - just give me a bunch of headers and source files, and maybe a readme with a list of configuration defines).

0 comments

3 comments · 1 top-level

dieortin2y ago· 2 in thread

> the more I'm exposed to languages with "proper" dependency management the more I appreciate the C way of just copying external library sources into the project

And why is that? I find it really cumbersome.

flohofwoeOP2y ago

What's cumbersome about copying a couple of files and adding them to your build scripts? At least that way you have complete control over the entire update and build process, you can use the build system of your choice, and you know exactly that there are no 'surprises' lurking in your dependency tree. It also nudges you to avoid libraries that come with complex build requirements (which will always pay off long term).

dieortin2y ago

Updating third party dependencies becomes much more cumbersome, as copy pasting isn’t really the most reliable way to update stuff. You lose all traceability with upstream, and their code becomes much harder to distinguish from your own. It also increases the size of your repositories by a lot.

j / k navigate · click thread line to collapse