3 ms·
To me this seems like (I'll admit I only watched a video and haven't tried it) it tries to solve a very complex problem of allowing multiple live editors of the
by alkonaut 9y ago
To me this seems like (I'll admit I only watched a video and haven't tried it) it tries to solve a very complex problem of allowing multiple live editors of the same file (?). Is that a solution in search of a problem?
When you pair program with someone, or assist someone, for it to have any point at all isn't the idea that you always edit in ONE place, and that only one person edits at a time? How will personA know what personB is doing otherwise, if personB's cursor can be anywhere?
Next, when personA and personB agree they have gotten somewhere and they launch their calculator app, web browser or whatever, how will both see what is going on? Is there support for also sharing a window/desktop? I mean, sharing my debugger state is cool, but what about the actual program window we are debugging? How can Jeff help me by introspecting variables in my program, if he can't see the program window?
The simpler problem of "sharing a screen while coding" seems to me to be a solved problem: you share your screen and input, like any remote desktop solution has done for ages. I get that this is significantly lower bandwidth and more tailored to coding, but in return it seems to not solve many of the fundamental problems of collaborative development.
I can see this tech being much more usable to e.g. develop cloud based IDE's, or remote debugging on servers, than "collaborative development"! Am I overly pessimistic or missing the point?
- lostintangent 9y agoPM on the Live Share team here. In many cases, yes, all collaborating participants would likely be working together in the same file. However, when speaking with folks as part of developing Live Share, we found that there were equally as many cases where developers wanted the ability to take certain actions independently (e.g. look up the definition of a function that’s in another file), without needing to disrupt the other parties, and without losing the ability to re-synchronize their focus once they were done. With that in mind, our goal for Live Share is to support “opportunistic collaboration” between developers, that supports a broad spectrum of needs/workflows/personal preferences/etc. in a way that potentially feels more natural for folks as they are helping/teaching each other (e.g. sometimes I want to tell you what I’m thinking, and sometimes I want to show you). Regarding your comment about being able to view the running app while debugging, we actually support the ability to “share local servers”, which allows this exact scenario for web apps/APIs/etc. https://github.com/MicrosoftDocs/live-share/blob/master/docs/collab-vscode.md#sharing-a-local-server https://github.com/MicrosoftDocs/live-share/blob/master/docs... It’s still early days for us, but it’s our goal that all meaningful editor/application context can be shared between participants, in order to effectively collaborate together (e.g. build output, terminal sessions).
- mcny 9y agoI know I've been (overly?) critical of Microsoft projects in the past but for what it is I continue to be impressed by Visual Studio Code. Thank you for your work in Visual Studio Code. I appreciate how it works across-the-board in fedora to a 32 bit Ubuntu based machine. I am also glad you're pursuing difficult goals like opportunistic collaboration. By the way, have you looked into data usage (sorry for wrong word) I mean is live share usable over a stable 200KBps connection? An unstable 1MBps LTE connection?
- lostintangent 9y agoWe’re still pretty early, and so we have lots of room to improve our network usage, and tolerance to instability. However, it’s absolutely our goal for Live Share to perform well (as well as can be expected?) on lower-bandwidth and volatile network connections (e.g. coffee shop WiFi). Currently, it’s already very usable in these conditions, especially when compared to screen sharing :)