Compilers and interpreters, unless they're running on bare metal, which is very niche, talk to the operating system using something called 'system calls' to ask for resources that they can't provide themselves, like virtual memory space and IO. These system calls are documented in C.
For example I wrote a Ruby compiler in Ruby, but I still need to know about the mmap system call, which is documented in C, to allocate my memory.
https://github.com/chrisseaton/rhizome/blob/main/doc/memory....
https://man7.org/linux/man-pages/man2/mmap.2.html
https://github.com/chrisseaton/rhizome/blob/main/lib/rhizome...
Sure, but the compiler will still have to generate machine code for those.
Maybe... MAYBE you don't have to read this book.
Where did I say I have to read it or that the author should learn another language? Nowhere. I said I wish it wasn't using C so that I could read it more easily.
There are many materials, compilers, and interpreters that use ocaml and haskell, for example. C isn't the only one. That's why I'd prefer pseudo code instead of C, so that I could use this book without learning a specific language only for it.