Comment by dheera
1 year ago
VNC doesn't even share your screen, it creates its own offscreen screen and doesn't even load your desktop, and uses some unusable minimalist window manager with a stupid X cursor. Yeah I could probably figure out how to get it to work but it's a chore. Terrible product design.
I've been wanting to create something WebRTC based, I'm not happy with either VNC or RDP.
On Windows, you do share the screen. I haven't seen any VNC servers that give you a new session like Terminal Services would.
On Linux, I've used both kinds of VNC server. One does start a new X instance, while the other one shares your main X instance. At the time I tried it, it was "TightVNCServer" to get a new X instance, and "X11vnc" to share the existing session.
TigerVNC x0vncserver[0] is just one option for ezpz sharing your existing X session.
Couple it with novnc if you want it in the web browser. Currently WebSockets but WebCodecs support looks to be around the corner[1].
> Terrible product design.
Which "product" are you even talking about here? VNC is a protocol with several different implementations.
[0]: https://tigervnc.org/doc/x0vncserver.html
[1]: https://github.com/novnc/noVNC/pull/1876