I love this! I have done a lot of CS research lately, and some of these I haven’t come across yet.<p>Let me share some of my favourites not listed here, off the top of my head:<p>- Ian Piumarta’s “Open, Extensible Object Models” (<a href="https://www.piumarta.com/software/id-objmodel/objmodel2.pdf" rel="nofollow">https://www.piumarta.com/software/id-objmodel/objmodel2.pdf</a>) is about creating the most minimal object-oriented metaobject system that allows the maximum amount of freedom for the programmer. It basically only defines a message send operation, everything else can be changed at runtime. The practical counterpart to the dense “Art of the Metaobject Protocol” book.<p>- John Ousterhout “Scripting: Higher-Level Programming for the 21st Century” (<a href="https://web.stanford.edu/~ouster/cgi-bin/papers/scripting.pdf" rel="nofollow">https://web.stanford.edu/~ouster/cgi-bin/papers/scripting.pd...</a>) - not really a paper, but an article from the creator of Tcl about the dichotomy between systems programming languages and scripting languages. Obvious at first sight, the lessons therein have wide ramifications IMO. We always seek the perfect multi-paradigm language that can do anything at high performance with the most productivity, while perhaps it is best to have compiled, fast, clunky systems languages paired with ergonomic, flexible interpreted frontend. Often all you need is C+Tcl in the same app. A must-read for anyone writing <i>yet</i> another programming language.<p>- Niklaus Wirth's Project Oberon (<a href="https://people.inf.ethz.ch/wirth/ProjectOberon/" rel="nofollow">https://people.inf.ethz.ch/wirth/ProjectOberon/</a>) is the implementation of an entire computer system, from the high-level UI down to kernel, compiler, and a RISC-like CPU architecture. He wrote the seminal "plea for lean software" and actually walked the walk. A long lost art in the era of dependency hell and towering abstractions from mediocre coders.