Say no more - I understand where this is coming from. Another complaint of sorts I had is that the book draws on too much source code, especially in the kernel part of it. I aim to make the 2nd edition as code free as possible, replacing code snippets with flow charts and other diagrams, as well as comparisons to other OSes.

I know that a lot of people struggle with how [vmmap] works and I've been doing to research with this.I think that perhaps a couple of pages on the subject would be welcome. Reading stackoverflow or other forums, people have problems trying to figure out how vmmap can get the information that it needs. Turns out that vmmap is quite interesting in the sense that itself, it does absolutely nothing everything is done in the Symbolication private framework. Obviously, that framework with does some mach_vm_region_recurse() but it also scans the memory to get some more info.

I'm currently dumping the dylib cache (contained inside a submap of the task), which is an interesting exercise but I haven't been able to make the address mapping work yet

I'd love to see more about code signing, especially for iOS. How both the actual signing and the runtime checks are implemented. How Apple leverages its PKI: dev certificates, provisioning profiles, entitlements, etc.

My "wishlist" is rather long, but dream about "The Ultimate" book is so beautiful...My list mostly related to iOS. Part of it I wish to know, part of it I already know, but I were happy to read it, when I read first edition.

So, the good news is - it's not too late. But LLVM is out of scope for the book, because it's a compiler technology. I will, however, be covering SWIFT in depth. As for Dtrace, you're totally right. I covered it all too briefly, and didn't touch on the implementation at all! I'll add that in, but it will likely be in Part II (dealing with the kernel). Thanks ! As for the watch - it will be covered - I'm adding a new chapter on hardware. And entitlements, rest assured, will be detailed as never before, as will code signing (which I will be showing at my RSA 2015 talk).