this post was submitted on 07 Sep 2023
61 points (98.4% liked)

Programming

17524 readers
348 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi
61
How important is the option for dynamic linking (vs static linking) in the modern day? (lemmy.ml)
submitted 1 year ago* (last edited 1 year ago) by cyclohexane@lemmy.ml to c/programming@programming.dev
61 comments fedilink hide all child comments
 

There was a time where this debate was bigger. It seems the world has shifted towards architectures and tooling that does not allow dynamic linking or makes it harder. This compromise makes it easier for the maintainers of the tools / languages, but does take away choice from the user / developer. But maybe that's not important? What are your thoughts?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] cyclohexane@lemmy.ml 11 points 1 year ago (1 children)

From my understanding, unless a shared library is used only by one process at a time, static linking can increase memory usage by multiplying the memory footprint of that library's code segment. So it is not only about disk space.

But I suppose for an increasing number of modern applications, data and heap is much larger than that (though I am not particularly a fan ...)

[โ€“] robinm@programming.dev 2 points 1 year ago

The gain in RAM are not even guaranteed. See my other comment