I was intrigued by the microcorelabs examples since they seem to be drop-in replacements for the hardware and are capable of running timing-dependent games and demos. Basically equivalent to the hardware, with the same input and output signals and timing. Note the 68K emulator was implemented on an Arduino-compatible Teensy microcontroller board rather than a full-blown Linux PC - though it does support 8GB of RAM, much more than the Mac it was plugged into!
If a device has the same input and output signal timing as the original hardware, then the implementation - be it custom silicon, FPGA, or software - is largely irrelevant to its functionality.
Regarding parallelism, it doesn't really matter as long as the output signals settle in time to meet the clock boundary.
I agree completely regarding the difficulty of getting input and display timing to work properly in a software emulator, especially running on a PC with a modern OS.
MB, darn those autocorrecting fingers ;-) I guess potentially the Mac in question could support 8MB, perhaps via a similar CPU daughterboard; of course now people complain about 8GB not being enough in entry-level Mac configurations.
If a device has the same input and output signal timing as the original hardware, then the implementation - be it custom silicon, FPGA, or software - is largely irrelevant to its functionality.
Regarding parallelism, it doesn't really matter as long as the output signals settle in time to meet the clock boundary.
I agree completely regarding the difficulty of getting input and display timing to work properly in a software emulator, especially running on a PC with a modern OS.