Why are we still messing around with ancient technology like VNC? Its terrible. It just samples screen output; it does not intelligently understand the underlying GUI so it can't really cache anything or accelerate anything.
If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP.
Still, I'd argue that HTML as a poor man's interface is perfect. I could sit down a write a HTML-based control panel that uses next to no resources. With VNC or whatever, now I need X running on my server, a GUI window manager running, and need to write a desktop app. This isn't progress.
If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP.
Well, I certainly won't argue against that. But at least with VNC it's being used for the purpose it was developed for. Personally I feel like trying to build complex application UIs with HMTL/CSS/Javascript is trying to shoehorn a square peg into a round hole. Browsers are great at, well, browsing hypermedia. I'd like to see that continue and the adoption of something like RDP, NX, or $NOT_INVENTED_YET for remoting interfaces.
But HTML isn't usually "remoting" an interface anymore, it _is_ the interface. This trend will only continue and solutions like VNC, NX will become unnecessary.
If we're going to replace HTML as a "poor man's interface" then we need to do better than VNC. Perhaps NX or RDP.
Still, I'd argue that HTML as a poor man's interface is perfect. I could sit down a write a HTML-based control panel that uses next to no resources. With VNC or whatever, now I need X running on my server, a GUI window manager running, and need to write a desktop app. This isn't progress.