Of course, that goes without saying. I meant it is the framework of all the earlier games machines/computers. In actual fact a modern Pentium class PC @ 3GHz struggles to do some of the things an Amiga could do (seamlessly anyway) due to extensive operating system issues (non-realtime) and the most expensive thing of all which is retargetable graphics. Early machines benefitted from the afct that everything was designed from the ground up for a particular screen size and depth.
Some of the arcade machines from around the mid 90's used clever hardware techniques to address CPU shortcomings of the time which are compute expensive in SW so there could be issues there as well.
Let's put it into the following frame of reference:
8-bit games machines.
For me personally those older games were a lot more enjoyable than a lot of the subversive reality games of today.
Well, it really depends onthe complexity of the emulator. Emulating old NES games isn't too difficult, however if you were to attempt to emulate an Xbox360, you'd find yourself getting nowhere. The last time I played with emulation a pretty strong computer struggled with Nintendo64 emulation. It has been a while though.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.