> avoid learning about the whole compiler toolchain with stuff like header only libraries.
Compromises needed to compile code on PDP-11, etc. are not some sacred immutable facts about how toolchain ought to work. One could learn everything about the crufty compiler toolchains and decide that it's all just a layering of over-abstracted nonsense over obsolete nonsense.
Compiler toolchains are hardly compromises needed to compile code on a PDP-11.
I do agree that UNIX compilation model is not the best example around, though.
Nonetheless, most languages on UNIX like OSes will for the most part follow the same model, as they need to fit into the ecosystem, as otherwise there is always an impedance mismatch that will prevent their adoption in some cases.
That is how you get modern languages like any wanabee C or C++ replacement using the same compiler toolchains and linkers, instead of compiler based build and linker systems, as languages not born into the UNIX culture.
Thus pretending systems programming languages are like scripting languages will hardly help.