Why does Linux load average include processes that are blocked on swapping. (Never realized they did; thought it used the classical definition). You know it's good software archaeology when it's treating with something that's still relevant today, and the search bottoms out in MACRO-10 code.
> font-size is the worst.
Just how hard coan it be to determine which font size should be used for an element based on the CSS? Pretty damn hard, it turns out.
> To recap, we are now at four different notions of font size being inherited: ...
Why and how to deprecate a programming language.
The thesis here is that the Linux kernel isn't a monorepo. Instead it's a monotree with multiple repositories. There are multiple repositories, e.g. the main one by Linus, subsystem specific ones, etc. Hence not a monorepo. But all of those repositories are rooted in the same tree, with changes flowing between the repos arbitrarily (so they're not polyrepos, which would generally need to be totally independent of each other). Hence the need for the new term.
Unsurprisingly, Github doesn't support this fairly unique workflow.
Computer science paper recommendations from Fabien Giesen, with long summaries of exactly why these papers are particularly useful/interesting.
A HN comment from 2015 explaining why the 6502 instruction set encouraged a SOA layout over AOS.