4 ms·
It depends, even a book "documenting the process step by step" could be a lot of things. Is it a tutorial? Is it an interesting discussion of emulation that use
by Someone1234 11y ago
It depends, even a book "documenting the process step by step" could be a lot of things. Is it a tutorial? Is it an interesting discussion of emulation that uses the construction of one to frame that discussion? It is device specific? Is it about that device or is it about all devices, again framing things?
The book itself sounds fine. The way you're selling the book (both on here and on LearnPub) could be improved. You need to decide what the point is REALLY meant to be, sure the theme is emulators, but if you have to describe it without using the word emulators or talking about any specific tech, how would that sound (e.g. "educational," "history," etc).
- cpro 11y agoThanks! You are absolutely right. The book is still taking shape and there is a lot that is unclear. I certainly have a lot of decisions I need to make on the structure of the book and how to make the purpose of the book more clear. In my mind the book is code-heavy and first goes through the design and implementation of your own virtual machine. The book then builds on top of the custom virtual machine with more techniques/architecture (changing the main loop from a classic switch statement to a jump table, discussing dynamic (just in time) compilation, static recompilation approaches etc). The ultimate goal is to take all of the design and approaches and build an emulator to spec that runs games you can find around the net. In particular, the Chip-8 system because the size of the project would be good for the book. I think it would be great to make the book more general than emulation/emulator development but at the same time I want to make it clear if you are a person interested in making emulators (like I was) then this is a book that will help you do that.