this post was submitted on 07 Sep 2023
62 points (94.3% liked)

Programming

17488 readers
123 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 [email protected]



founded 1 year ago
MODERATORS
 

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
[–] 0x0 0 points 1 year ago (1 children)

Which is why libraries are versioned. The same version can be compiled differently across OSs, yes, but again, unless it's an obscure closed library, in my experience dependencies tend to be stable. Then again all dependencies i deal with are open source so i can always recompile them if need be.

More work? Maybe. Also more control and a more efficient app. Anyway i'm paid to work.

[–] [email protected] 2 points 1 year ago (1 children)

More control? If you're speaking from the app developer's perspective, dynamic linking very much gives you less control of what is actually executed in the end.

[–] o11c 2 points 1 year ago

The problem is that the application developer usually thinks they know everything about what they want from their dependencies, but they actually don't.