Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Live Share

code.visualstudio.com

Post reply on HN
Print view View original

21–30 of 115 posts

Re: Visual Studio Live Share

#21

Post by lostintangent »

kumarvvr wrote: post #19
lostintangent wrote: post #13

Earlier quoted context omitted.

We're definitely very serious about Visual Studio Code :)

Just saw the shared debug feature. Really really cool. Mind literally hit a breakpoint.

That's great to hear! We definitely believe that collaborative debugging is a critical component of being able to demonstrate/reproduce issues, as well as validate changes made during a collaborative/pairing session. We look forward to seeing how folks end up using it :)

Re: Visual Studio Live Share

#23

Post by andr »

Please, please make a headless mode for this! My ideal use case would be to run this on a development VM and be able to connect to it with my VS Code and debug live on the VM. This would be a much better experience than rsync-ing your changes on every run.

Re: Visual Studio Live Share

#24

Post by segmondy »

alangpierce wrote: post #17

The demo showed this as an alternative to screen sharing, but I could also see this feature being really useful for pair programming and providing in-person help. Even when I'm standing next to someone, it's nice for me to be able to poke around in their code on my own laptop, especially if I can type in examples of things I have in mind if I make a suggestion.

My own opinion, but it's not pair programming if everyone doesn't have their own keyboard and mouse. When I've practice pair programming, either I screen share with screen/tmux where anyone can take over and type or if at the same computer have multiple keyboards and mouse. Both programmers must be active. With only 1 input we end up in a passive/active scenario, which is fine for mentoring.

Re: Visual Studio Live Share

#26

Post by chuxel »

Rovanion wrote: post #22

So this is exactly like Saros for Eclipse? https://youtu.be/ISM83tLYQ-Q?t=76

PM at Microsoft. Beyond co-editing, Live Share enables co-debugging which allows you to track down problems that only happen on one machine in a low latency environment and enable concurrent investigation of different variables or stack points against the same running app. We've got more features in mind to enable end-to-end development. It also follows a model that actually does not require sync'ing at all which gets you up and running fast and improves security.

Re: Visual Studio Live Share

#27

Post by coldtea »

SantiagoElf wrote: post #2

Cool sounding feature, but in practice remote code sharing and working on the same code is to extreme programming as 'phone sex' is to sex. :)

Given that "extreme programming" is a meaningless buzzword, whereas the developments shown sound actually useful, that's probably for the better.

Re: Visual Studio Live Share

#28

Post by rightos »

jonwchu wrote: post #7
adpirz wrote: post #6

Pretty cool, but I wonder what the implications are for code privacy given that this runs through Microsoft's servers. Will they also be collecting data on the code being shared? Especially given the Kite debacle, think it's important to be clear up front.

Hey there! Another PM on Visual Studio Live Share here. Security is absolutely something we are designing for. Microsoft will not be collecting data on the code. The code is not stored or uploaded in the cloud in any way. Rather, it is just a connection that is established between you and the teammate you are sharing with. There's more details in the FAQ here: https://code.visualstudio.com/docs/supporting/live-share-…

That FAQ seems fairly vague - what I'm looking for is simply how connections are established - can I simply point the thing at another copy of VSCode running in my LAN? Or do I have to involve Microsoft servers on the internet for session setup? Is the connection directly between us or via an MS server? What encryption is performed and where? Can a Microsoft employee or someone who compromises them theorically gain access to my code simply by accessing my coworkers account and connecting to my session?

Re: Visual Studio Live Share

#29

Post by tzahola »

jonwchu wrote: post #7
adpirz wrote: post #6

Pretty cool, but I wonder what the implications are for code privacy given that this runs through Microsoft's servers. Will they also be collecting data on the code being shared? Especially given the Kite debacle, think it's important to be clear up front.

Hey there! Another PM on Visual Studio Live Share here. Security is absolutely something we are designing for. Microsoft will not be collecting data on the code. The code is not stored or uploaded in the cloud in any way. Rather, it is just a connection that is established between you and the teammate you are sharing with. There's more details in the FAQ here: https://code.visualstudio.com/docs/supporting/live-share-…

Really? So Microsoft just provides name resolution, and the data goes peer-to-peer?

Or maybe this “connection” is actually going through your servers and we have to take your word for not peeking inside the packets?

Re: Visual Studio Live Share

#30

Post by dep_b »

cjsuk wrote: post #4
dep_b wrote: post #3

Screen sharing is such a drag using Skype. Everything goes slow as poop even on the fastest of MacBooks. Yet for a lot of purposes doing a screen share is super valuable. I imagine Live Share is much leaner much alike watching somebody changing a Google Doc in front of your nose.

Personally I'd find it irritating, as I do with Google Docs. This is a neat gimmick but I don't think it'll revolutionise anything or end up being the status quo in the future.

Well Google Docs still is less irritating than screensharing what you are doing in Google Docs via Skype.
Post reply on HN