linker

For example passing a function pointer to a different library (callback) the linker is completely oblivious to.

I need to point out that your second point about the linker is totally false.

This is an in-depth introduction to linkers by Ian Lance Taylor, the author of the gold linker.

That's a lot of work for something that the dynamic linker on OS X supports out of the box.

This isn't a language intrinsic problem: it boils down to the linker model, which only C and C++ share.

If you do a static link, the linker can at least remove most of the bloat you don't use.

A optimizing linker pulling together static libraries is going to make page-merging the executable almost impossible.

Yeah, but that is a consequence of not having a Rust aware linker and relying on one that basically uses C semantics.

Before reading this I thought I knew what linker did and how it worked, this series set me straight.

I went from no knowledge of 6[cl] (the amd64 compiler&linker) to pretty comfortable with the source in about 2 days.

The thing I like about clojurescript is the fact that it has a linker and library system which makes sense.

The automatic translation of the compiler and linker from C to Go resulted in unidiomatic Go code that performs poorly compared to well-written Go.

The C compiler and associated tools (assembler, linker and simulator) are included in the CD." I looked at Mark Shannon's page below but didn't find a link to an ISO image of the mentioned CD.

It appears according to the abstract that it beats other languages while being implemented as "just a library": "Our library-only implementation (...) For many uses, it equals or outperforms equivalent code in languages with built-in type-switching constructs, such as OCaml and Haskell" In my opinion major weakness of C++ is just that the linker features more or less remained out of the language design.

--> Linker's not needed, and there are many package managers that work pretty good.