Hey dev.to 👋
I've just published a new series about operating systems: what actually happens between your programs and the hardware.
The previous series took a computer apart. This one opens it up: how one CPU ends up running a browser, an editor, and a hundred background services at once, and how the kernel keeps control of the machine while barely running.
The goal is to understand the OS from the ground up, one concept at a time, from syscalls to the power button.
This is the first post in the series (1/8): https://www.wesleybertipaglia.com/blog/zkb3xkdy
If you've ever wondered what the boundary between your code and the machine really is, this is where the series starts.
Top comments (0)