5 ms·
How does this differ from running a VNC client inside any browser?
by bitL 12y ago
How does this differ from running a VNC client inside any browser?
- martinald 12y agoIt is more like a VNC server than a client.
- dudus 12y agoIf you try it out you'll notice that it's just better. I don't know the internals of it, but I suppose it uses more modern codecs for transmitting the screenshare. The experience just feels a lot snappier.
- vfclists 12y agoIt probably has its own intermediate proxy which doesn't require firewall configuration? It is probably better optimized as well.
- panzi 12y agoIt probably has its own intermediate proxy with a "lawful" intercept interface (i.e. pies everything to the NSA). Well, I wouldn't be surprised if that conspiracy theory would be true.
- ossreality 12y agoAbsurd nonsense. I have as much reason to believe that panzi is breaking into my house at night and fondling me.
- masto 12y agoI wouldn't be surprised if that's a load of bullshit.
- panzi 12y agoWell, I don't know about that, but it is law that services over a certain size have to have a lawful intercept interface (e.g. Skype has one) and it is know that this interface gets abused by secret services.
- georgemcbay 12y agoVNC (even the various 'Tight', 'Lite', 'Whatever' variants) is horribly slow -- usable in a pinch, but every UI/UX interaction is just delayed enough that nothing feels 'right'. Chrome Remote is much more responsive, it feels more like Windows Remote Desktop Protocol speeds, perfectly usable almost as if you were local. Also it does initial connection handshaking so if you login to chrome from machine B and machine A is already set up for Chrome remote you can just connect there via a list of endpoints without having to know the external-facing IP address and/or setting up firewall tunneling.