News for hackers. Stuff that matters.

A comment on Best practices for a new Go developer. Parent comment

Re:Best practices for a new Go developer by jerrac on Wednesday September 02, 2015 @05:42PM (#10162083)
It's been a few years since my last C++ class, and I haven't done any compiled programming since. So I either completely forgot about static linking, or it just didn't get covered.

Why have I seen several go apps that use static linking, but every C or C++ app I see uses dynamic linking?

A quick google makes me think that the main downsides to static linking are resources and upstream bugs. Those issues would apply to go the same way they'd apply to C. Right? So why does it seem (from my limited experience) that go uses static linking more than other languages do?

[ Parent | on HN ]
Re:Best practices for a new Go developer by pjmlp on Wednesday September 02, 2015 @06:16PM (#10162266)
The authors are very vocal against dynamic linking.

http://harmful.cat-v.org/software/dynamic-linking/

Modern applications use dynamic linking most of the time, because despite the possible headache with versions, it offers a much more flexible architecture.

[ Parent | on HN ]