101–110 of 115 posts
I desperately need something like this especially when I'm working with junior devs. I'm usually pretty busy so I often ask them to get the debugger to break at just the point where they are having an issue before I walk over to their desks and take over.
This would be heaven sent.
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…
Is it relaying the data over Microsoft (or Azure/Skype/etc) server? Or is it a point-to-point / peer-to-peer connection? And if it relays the shared data over Microsoft server, what data beside currently opened source code files and keyboard + mouse inputs is transfered? Will it also transfer more source code files (e.g. whole VS project)? I have to say this feature reminds me of the hollywood movie "Startup" (2001):…
We don't transfer all keyboard and mouse inputs. Instead, we communicate the data behind each collaboration activity (e.g. opening and editing source files, initiating debug sessions, stepping through code, etc.). We only transfer what is needed during the collaboration session.
Earlier quoted context omitted.
Wow, this is awesome. While the use case outlined here is great I could probably use this as a remote editor. That is, I can have my dev environment running in the 'cloud' and still expect responsiveness from my editor!
Remote development is definitely an adjacent use case that we believe could be really compelling. Thanks so much for providing the +1 on the scenario, and stay tuned (i.e. sign up :)) for future updates!
edit: grammar
Atom announced "Teletype" today: https://blog.atom.io/2017/11/15/code-together-in-real-time-w...
While Atom's Teletype works today. VSC Live Share is still unreleased "vamporware" (a term coined by MSFT). The ripping of Atom, rebranding it as VSC and doing a press release for such vital new feature is I guess pure coincidence, and not a typical tactic they are known for, right? Edit: > That's just patently false. Curious, how can it be patently false when "Visual Studio Code is based on technology from Github’s…
Lots of stuff is built on Electron. (Desktop Slack, Discord, Atom, VS Code, Kitematic, GitHub Desktop, etc.) Electron is not an editor framework.
Your statements remain patently false.
Am I the only one who finds it ironic that the development teams behind the top two open source editors introduce support for collaborative editing on the dame day, apparently unaware that they were both working on the same thing, and there being no evidence of collaboration between the two?
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.
Yes please, that would be awesome! I have a workstation that I rdp into from all over the world in order to do development in VS and the experience is terrible when I am on the other side of the world because of high latencies and low bandwidth link. Being able to connect to the workstation's VS directly and edit files + start debugging sessions remotely, that would be fantastic!
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.
My thoughts as well, I can't imagine they haven't thought of it, here's hoping, especially since the PM commented in this thread.
How well do these tools generally handle poor latency? I often work remotely over 3G/4G. Voice is fine, as is simple screen sharing of stuff like Trello boards in a meeting. I tried Slack's screen collaboration and it was hardly usable though.
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…
[1]: https://code.visualstudio.com/docs/supporting/live-share-faq...