Change "Systems" to "Machine systems" and limit its scope?

[joshmhanson]

Arguably, everything in the curriculum is part of some "system". The category we have for this is pretty vague.

I want to rename "Systems" to "Machine systems", limiting it to a discussion of low-level systems and their associated DSLs like C (and later, Rust).

Currently, "Core Systems" includes networking. The material we end up using for networking is in question per #520. Networking should be moved to "Structures" if the material we're using is more theory-focused, but it can be kept in "Core Machine Systems" if it's implementation-focused.

I also want to add materials on Rust and on programming low-level systems using Rust to "Advanced Machine Systems", because currently all of that material is done with C, which puts our curriculum decades behind the state of the art. There aren't any full MOOCs yet on using Rust for low-level systems, but we can at least put what we have on there.

[joshmhanson]

On second thought, "machine systems" might be puzzling. There is no corresponding term in industry nor in academia.

"Systems" is slightly too broad, I think, because many systems are very high-level, with business logic provided by domain-driven design.

The "systems" I have in mind are those whose primary business is to talk to a machine. "Computing Systems" might be okay: systems for turning inanimate objects into machines that can perform computations.

Still unsure how to deal with Databases and Networking.