The guy doing the article about emulation performance does not understand the basic concept of a low level emulator.
Your XBox 360 games run shittier on the Xbox One than the 360 not because it is so hard for the XBOne to process the internal workings of the 360! It is difficult because the emulator IS THE INTERNAL WORKINGS OF THE 360 and that hardware doesn't hang well with VSync.
Low level emulators cannot run faster than the original hardware or else it's not really such a low level emulator, now is it?
You can take the high (level) road and go high level emulation where you can get great performance and graphics but.... hardly anything will work and you'll have to tinker endlessly with the code and probably let others take on the project for you at some point. UltraHLE (the N64 emulator) was notoriously horrible on compatibility despite running Mario 64 like a dream.
Then there's the low level emulator approach which actually emulates the hardware itself. This is not about getting games to "just work" like a high level emulator... this is about recreating the actual hardware, which includes all of those little problems like the glitches on NES games and the shitty performance on others.
Low level emulators have excellent compatibility because they aim to essentially BE the actual hardware as far as the source code's interaction with the system goes.
Oh, and enjoy running what's left of those 32 bit programs and Windows XP apps that you're running seamlessly through an emulated environment on your computer. All 32 bit programs and non recent programs (not built for 7 or 10 for example...) CANNOT be processed by a 64 bit, modern version of Windows so Microsoft made the WOW64 emulator.
Its use is quite apparent and it runs in the background. You can even play games through the emulator with no noticeable difference (there is some though...) in performance or input lag.
Don't believe Nintendo and Sony when they tell you that their new game consoles are backwards compatible and that they put in lots of engineering work to get that happening. It's total bullshit.
The reality of "backwards compatibility" is that it's NOT ACTUALLY BACKWARDS COMPATIBLE: you do not run Windows XP code natively in Windows 10. There is an emulator that runs seamlessly in the background tricking that program into thinking it's being processed by Windows XP when in fact it is not.
This comment was edited on Jan 22, 2016, 16:26.