rhizome

> I don't know what that has to do with learning about compilers and interpreters. 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...

There was actually an existing, similar in concept, Ruby JIT, Rhyzome: https://github.com/chrisseaton/rhizome. It's good to see (IMO) the development of a JIT in a strict sense. I'm personally skeptical about the current approach (invoking a compiler separately). On the other hand, it's important to know that JITs may take a long development time to be performant, and that they also complicate the performance profile of a virtual machine.

Lots of compiler tutorials are like this - there's very little out there to explain how compilers really work. This is my effort - trying to show genuine data structures and processes. https://github.com/chrisseaton/rhizome

Yeah, sorry, it was designed to be deep but not broad, and of course it's unfinished. It's a bit of a shame. The reading list is the starting point https://github.com/chrisseaton/rhizome#how-to-read-this-repo..., as is the code in lib of course. You can also run the experiments to generate programs before and after passes. Someone who knows about basic things like bytecode might like to start reading at https://github.com/chrisseaton/rhizome/blob/main/doc/constru... and may find that then starts to be new information.