Perhaps we're just doing it a different way, by making sure we have a solid core and ability to port to different devices easily - and then have a separate project to build interesting UIs..:

http://www.youtube.com/watch?v=7PMlgIoTuJ4&feature=plcp

http://www.youtube.com/watch?v=V83mChc-hQE&feature=plcp

But yes, the GLES-less ability of N8x0 is a problem these days. But even more so is the lack of power management in the kernel (that may have been fixed) and a PSM-able WiFi driver (may also have been fixed). Mer builds for ARMv6 because of N8x0 and Raspberry Pi.

If those two are fixed, there's no reason why you couldn't run qtquick1 things on that device. I still hate having my N8x0's sit idly around, too. But if we can't even find man-power in community for things like Nemo, it's going to be difficult for N8x0.

Personally I still want to see what kind of benefit we could get from a qt compositor sitting on top of the framebuffer with wayland clients on N8x0 and how much could actually be done with non-GLES clients.. but that's an afternoon project for another time.

(NOTE: we do know those videos show lag, and we know why, and it's fixed)