I imagine VNC can't do this well because it streams pixels with no optimizations other than antiquated compression (it can't even match WebRTC screen sharing), and crappy color depth.
The idea is interesting for lightweight computers e.g. chromebooks and ultrabooks, but it would irk me a lot to have my browser and personal information running on some other machine that I don't control.
What I would be super-interested in though is a self-hosted version of Mighty, that I could install on a Linux box anywhere of my choosing. For example, the server runs on my powerful desktop at home, and my ultrabook in the bedroom can be a client.
This project actually made me think that, since the X-Window protocol is practically a dead-end and everything's gotta be made with web tech now (ugh), it'd be really cool to have a version of FF or Chrome that's smart enough to send some kind of render instructions between a server-instance and a client-instance. Process server-side, render client-side, like X-Window but for web junk.
(the notion that this is completely fucking absurd since those "render instructions" are called "HTML" and I'm just describing server-side rendering isn't lost on me, but it's not my fault things have gotten so bad that having a server-side browser forward draw commands from bloated "web apps" to a resource-light client might actually be kinda nice)
The idea is interesting for lightweight computers e.g. chromebooks and ultrabooks, but it would irk me a lot to have my browser and personal information running on some other machine that I don't control.
What I would be super-interested in though is a self-hosted version of Mighty, that I could install on a Linux box anywhere of my choosing. For example, the server runs on my powerful desktop at home, and my ultrabook in the bedroom can be a client.