If you've ever used Remote Desktop / VNC, you know that it just doesn't work. The latency of the network communication is too great within your own local network over Wifi, enough as to be a pain in the ass for work, let alone when communicating over the Internet. And you'd better not be on a metered Internet connection, because these high-resolution screens will produce data like crazy.

I know it sounds cool in theory, but it just doesn't work, at all. Basically Remote Desktop / VNC is only useful for short sessions and/or debugging, not for work, unless you're in text mode with SSH, vim, screen, tools like that ;-)

>If you've ever used Remote Desktop / VNC, you know that it just doesn't work

I wrote a DOS VNC client in 1999 for my ThinkPad 720 (to access my Sun workstation at work from home), so my mileage varies. ;-)

We had lower screen resolutions and color depths then, but also slower connections. I've used VNC quite a bit over the years but admittedly, for working from home I used ssh (because it was sufficient and I use vi). FWIW, practicality greatly depends on your type of work. Typing text in an IDE and running the occasional debug session should be no problem due to the way screen updates are transmitted, anything graphics-heavy will be frustrating.