Nice series! One comment though: > The compiler ingests one .c and outputs one .o. It has a low memory footprint. The linker on the other side, must use all t

Nice series! One comment though: > The compiler ingests one .c and outputs one .o. It has a low memory footprint. The linker on the other side, must use all the .o files at once to generate the executable. Keeping all these .o in memory would stress the system too much on big projects. This is a really weak argument that does not make a lot of sense. The major advantage of separate object files is avoiding recompilation of modules that haven’t changed. In fact, compilers like Jonathan Blow’s Jai seem to get massive performance improvements by treating everything as a single compilation unit and avoiding writing a bunch of object files only to call the linker on all of them.