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

11–20 of 115 posts

Re: Visual Studio Live Share

#11

Post by adpirz »

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-…

Good to hear, thanks!

Re: Visual Studio Live Share

#12

Post by pvg »

lostintangent wrote: post #5

PM on the Visual Studio Live Share team here. Thanks for posting! We're really excited to hear folks thoughts about this experience, how it can help improve their existing team collaboration workflows, and how we can continue to improve/learn. So please sign up and/or let us know what you think :) We've heard pretty loud and clear that developers want better collaboration tools, without needing to switch editors, wit…

It would have been even better to include at least some idea of the expected release time or availability of the preview. It's hard to believe there is so much detail on the feature set, a big website to promote this and nobody at Microsoft has any certainty when this might be out.

Re: Visual Studio Live Share

#15

Post by martinsuchan »

lostintangent wrote: post #5

PM on the Visual Studio Live Share team here. Thanks for posting! We're really excited to hear folks thoughts about this experience, how it can help improve their existing team collaboration workflows, and how we can continue to improve/learn. So please sign up and/or let us know what you think :) We've heard pretty loud and clear that developers want better collaboration tools, without needing to switch editors, wit…

Wondering what will be the final pricing of this feature? It looks too good to be available for free for any VS/VSCode user.

Re: Visual Studio Live Share

#16

Post by [deleted] »

lostintangent wrote: post #5

PM on the Visual Studio Live Share team here. Thanks for posting! We're really excited to hear folks thoughts about this experience, how it can help improve their existing team collaboration workflows, and how we can continue to improve/learn. So please sign up and/or let us know what you think :) We've heard pretty loud and clear that developers want better collaboration tools, without needing to switch editors, wit…

[deleted]

Re: Visual Studio Live Share

#17

Post by alangpierce »

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.

Re: Visual Studio Live Share

#18

Post by nwah1 »

throwawayf238 wrote: post #14

Super no thanks. There's too much risk in this work for bloaty, spying type code to land in the editor because of this. I'm sure the team at Microsoft is super talented, but this seems like an awful product direction.

Strong second. I love visual studio, and visual studio code, but this particular feature would be extremely irritating. I'd also worry that it would promote awful development models like Pivotal's pair programming take on agile, which has always struck me as creepy and totalitarian.

Re: Visual Studio Live Share

#20

Post by chuxel »

throwawayf238 wrote: post #14

Super no thanks. There's too much risk in this work for bloaty, spying type code to land in the editor because of this. I'm sure the team at Microsoft is super talented, but this seems like an awful product direction.

PM at Microsoft. Thanks for the feedback - we're thinking hard about ways to ensure that the changes that land in your code is only that which you expect. Are there specific features that you'd need before you'd be comfortable using something like this?
Post reply on HN