> To summarize, what we call “systems programming” I think should be called “low-level programming.” Computer systems design as a field is too important not to

> To summarize, what we call “systems programming” I think should be called “low-level programming.” Computer systems design as a field is too important not to have its own name. Clearly separating these two ideas provides a greater conceptual clarity on the space of programming language design, and it also opens the door to sharing insights across the two spaces: how can we design the system around the machine, and vice versa? Alternate definition whose source I can't recall: Systems programming is everything that isn't application programming. Maybe it's time to update that with: Systems programming is everything that isn't application programming or low-level programming.