I learned some interesting compiler techniques from reading that book.
Anyone that actually programmed MS-DOS, knows that we used to program directly against the hardware for actual work. MS-DOS was nothing more than what is usually known as monitor in OS literature.
Continuing the texts from people more relavant to the CS world than me,
"An operating system is a collection of things that don't fit into a language. There shouldn't be one." - Dan Ingalls on
https://archive.org/details/byte-magazine-1981-08 https://www.cs.virginia.edu/~evans/cs655/readings/smalltalk....
"Building Parallel, Embedded, and Real-Time Applications with Ada" - John McCormick
https://www.amazon.co.uk/Building-Parallel-Embedded-Real-Tim...
"Project Oberon: The Design Of An Operating System And Compiler" - Niklaus Wirth
https://www.amazon.co.uk/Project-Oberon-Design-Operating-Com...
And not to let this just be theory, here are a few examples of commercial products using the language runtime to interface with the hardware.
http://www.astrobe.com/default.htm
I learned some interesting compiler techniques from reading that book.
I have the orginal hardbound 1992 edition [0], but it looks like there is a 2013 revision available as a collection of pdfs [1]
[0] https://www.amazon.com/Project-Oberon-Design-Operating-Compi... [1] https://inf.ethz.ch/personal/wirth/ProjectOberon/index.html
You are unlikely to encounter Oberon in the wild, but this book is the clearest and most elegant exposition of a systems design I have seen. They walk through the code for a complete operating system from hardware drivers to file system, compiler, graphic user interface and everything else in less than 10,000 lines of code. The focus on modularity and minimalism is very refreshing.