5 ms·

For collaborating on the code look at the Visual studio code feature called live share, which allows you to collaborate in real-time [1]. I've tried it and it

by neppo 8y ago

For collaborating on the code look at the Visual studio code feature called live share, which allows you to collaborate in real-time [1]. I've tried it and it worked well. [1] https://code.visualstudio.com/blogs/2017/11/15/live-share https://code.visualstudio.com/blogs/2017/11/15/live-share

DerJacques 8y ago
I agree that Live Share sounds like the perfect solution. You can even share ports, so your friend can access your development server.
Outpox 8y ago
I was going to suggest this as well. I've used it to explain some features to a friend while we were on Discord.
deepakkarki 8y ago
I'd it possible to share a browser window though? That's a key aspect for us! Thanks!
- notemaker 8y ago
  Yes, see Dylan Van Bommel's comment on Fun Fun Function's collaborative stream: https://youtu.be/_OTUGVAEWCA https://youtu.be/_OTUGVAEWCA
magnetic 8y ago
That looks very cool. 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?
- testvox 8y ago
  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/reference/security#connectivity https://docs.microsoft.com/en-us/visualstudio/liveshare/refe...
  - magnetic 8y ago
    Indeed, according to the page you linked: > Note that Live Share's cloud relay does not persist any traffic routed through it and does not "snoop" the traffic in any way. So it sounds like it's your traditional NAT traversal with TURN/STUN, and their promise that they don't snoop if the end up relaying. Very cool!
  - Sephr 8y ago
    Where on that page does it say how to disable the relay feature?
spinningarrow 8y ago
YMMV though. I tried it last month on a local network and the lag was quite unbearable with sessions often going out of sync.
nijaru 8y ago
Atom has https://teletype.atom.io/ https://teletype.atom.io/ as well. I don't have any experience with either though.
- rjzzleep 8y ago
  supposedly tandem leverages teletype work for vim and sublime https://github.com/typeintandem/tandem https://github.com/typeintandem/tandem
deepGem 8y ago
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.
voltagex_ 8y ago
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.

by neppo 8y ago

DerJacques 8y ago

I agree that Live Share sounds like the perfect solution. You can even share ports, so your friend can access your development server.

Outpox 8y ago

I was going to suggest this as well. I've used it to explain some features to a friend while we were on Discord.

deepakkarki 8y ago

I'd it possible to share a browser window though? That's a key aspect for us! Thanks!

notemaker 8y ago
Yes, see Dylan Van Bommel's comment on Fun Fun Function's collaborative stream: https://youtu.be/_OTUGVAEWCA https://youtu.be/_OTUGVAEWCA

magnetic 8y ago

That looks very cool. 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?

testvox 8y ago
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/reference/security#connectivity https://docs.microsoft.com/en-us/visualstudio/liveshare/refe...
- magnetic 8y ago
  Indeed, according to the page you linked: > Note that Live Share's cloud relay does not persist any traffic routed through it and does not "snoop" the traffic in any way. So it sounds like it's your traditional NAT traversal with TURN/STUN, and their promise that they don't snoop if the end up relaying. Very cool!
- Sephr 8y ago
  Where on that page does it say how to disable the relay feature?

spinningarrow 8y ago

YMMV though. I tried it last month on a local network and the lag was quite unbearable with sessions often going out of sync.

nijaru 8y ago

Atom has https://teletype.atom.io/ https://teletype.atom.io/ as well. I don't have any experience with either though.

rjzzleep 8y ago
supposedly tandem leverages teletype work for vim and sublime https://github.com/typeintandem/tandem https://github.com/typeintandem/tandem

deepGem 8y ago

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.

voltagex_ 8y ago

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.