Since when NES, PS1 and Saturn made me a happy guy, emulators for new consoles made me a sad guy.

I hate so much the focus on "practicality" and less accuracy.
-> The grow up of mobiles and devices as priority, a lot codes being made for it... More resource and research for a lot devices and OS.

We need some focus and vision for the future.
->Some consoles need a lot CPU or GPU. 64-bit is now, but new technologies coming to us. And we need some new codes and we can make new accuracy or high compatibility emulators of "not old consoles" on new PCs, but mobiles or some OS needs more power or different intructions.

More than emulation. Industry itself.
As you can see, a lot collection or ports without any work for nowadays. The experience is just bad or different. I can't feel the right thing playing Megaman III on the collection, even with some stupid filter. The work is so... wrong. And I need to create a filter to play on PC on original file using accurate emulator.

Well, arguably, PPSSPP is probably a lot less about accuracy than about speed, although we try. Some of it is the reality that we don't fully understand how it exactly works, and we're often doing hardware tests to narrow that down.

The NES ran at about 2 Mhz, which is less than 0.1% of modern systems. It had similarly slow RAM and everything else.

The PS3 has a 3.2 Ghz processor and 6 (usable by games) specialized cores. That's tough to emulate, it just is. And RAM access is much faster on this modern device.

So practicality is coming in because, really, it's just not useful to emulate at less than 5% speed. Which means you can't just build a 100% from scratch software model of the CPU units and make it cycle accurate.

As soon as you start translating things to the host instruction set, you start giving up accuracy on timing and sometimes calculation. Probably the host and guest processors deviate slightly in how they handle denormals. Prefetching might behave a bit differently. Branch prediction is slightly different.

The reality is that we're moving towards a place where we're scaling out CPU and GPU power - we've begun to hit a wall in effective speed. But emulating a CPU, because it depends on a relatively small register file, is mostly a single-threaded operation. At best, you do branch prediction and run basic blocks on separate cores and work it out later in your software model (sorta like modern CPUs already do.)

If you can think of a better way to spread out emulation to multiple cores, I'd love to hear it. Or maybe quantum computing will be amazing for emulation. But as we are now, we're hitting walls.

That doesn't mean accuracy isn't a goal, it just means it ends up being secondary.

I do think there's some possibility of specialized hardware to improve this. For example, imagine a usb dongle that does non-IEEE float operations the same way as a guest device. If it has low enough latency and is easy to access, this might be a practical way to increase accuracy without sacrificing a basic level of acceptable speed.

Practicality versus accuracy:
This will really depend on how much accuracy you think is enough. For example cycle accurate accuracy for even an SNES requires a pretty powerful CPU. If you wanted to try and incorporate cycle accuracy into something more modern then you're going to require even more exponential CPU power.

Focus and vision for the future:
While technologies like 64-bit and multi-core processors do help some emulation it is not always useful for every emulator. In some cases these Technologies might even cause overhead that can either slow down the Emulator or reduce accuracy. New does not always mean faster and more accurate.

The industry:
A lot of retro games I'm never quite look exactly right due to advancements in display technology. Little tricks were used in order to get the most out of underpowered consoles and these techniques don't translate quite right to modern displays and video rendering. This is less of an issue for consoles and handhelds that were built with LCD in mind. The example that comes to mind is the Quick Draw mini game in Kirby's Adventure for the NES. Emulating the NES version on an LCD screen makes the game nearly impossible to actually win do to refresh rates and the way the game is displayed. If however you use a Gameboy Advanced emulator and the Gameboy Advance version the game was tweaked in order to work on the systems LCD screen and as a result the mini game even through emulation is much more... fair. Another example would be the game 7th Guest where the microscope puzzle was based around using the computer's processor to determine how hard the puzzle was. This becomes a slight issue on more Modern Hardware where are the puzzle becomes nearly impossible to actually beat. Due to odd issues like this porting old games to new systems is somewhat more of an art then an exact science. I do agree that there are way too many lazy ports though, but that has been in Industry standard for decades.

Even some retro systems aren't very supported by emulation. Admittedly they're less popular systems, but still...

Atari Jaguar - I wouldn't classify any of the existing emulators as anything other than beta. They don't run a bunch of games and the ones they do run often don't run well.

Coleco Adam - I know of one emulator for it and it's ancient. BlueMSX were supposed to add support for it at some point, but the entire BlueMSX team seems to have vanished.

X68000 - Big in Japan and had some great arcade ports. There are a couple semi-decent emulators, but they're in Japanese and not very full featured.

Vectrex - There's a couple emulators, but they're pretty bare bones.

Acorn Archimedes - There's a bunch of emulators for this system and they all pretty much suck. Some of them don't even seem to work, some crash when trying to run software. Of the ones that work, they have none of the usual features you expect, like save states or joystick support. Apparently only one model of the Archimedes had a joystick port and most games are played with the keyboard, so you'd think the authors would incorporate some kind of joy-to-key functionality, but they didn't. There's even a ridiculously expensive commercial emulator, but apparently they hard-coded floppy drive 0, the drive that all software expects to be booted from, to use an actual drive, because so many machines today come with 3.5" floppy drives..?