I've tried it. It's... promising but very strange. A session between two people in the same Australian town was bounced via a server in the US. We had screen sharing via Discord at the same time which was far more responsive (but 720p, ugh).
The current implementation uses temp files everywhere and an odd way of driving Visual Studio. I'm really keen to see where this goes in the future.
You had me at the shared debug session. I am amazed at how VSCode has evolved in such a short span of time. Technically it's not an IDE but it has most of the required features of the IDE.
The liveshare feature does require you to be signed in to Github or Microsoft. So the sharing might not work with other proprietary SC or even Bitbucket or Gitlab.
With the "rendez-vous" URL being hosted by Microsoft (it looks that way in the video), does it mean your source code is sent to Microsoft, or does the server-side simply act as a relay to facilitate communication between 2 endpoints without needing to be exposed to the code?
It may be sent to microsoft if a direct connection cannot be established between the liveshare clients (due to firewall/nat issues). In that case microsoft's servers act as a relay for both clients and therefore your code would be sent to microsoft owned servers. This relay feature can be disabled. More information available here. https://docs.microsoft.com/en-us/visualstudio/liveshare/refe...
I've tried it and it worked well.
[1] https://code.visualstudio.com/blogs/2017/11/15/live-share