I haven't used VS Code Pair Programming yet, but again, assume it's very functional as well. Their screen sharing/remote control is very functional. I use MS Teams at work at a large organization and Microsoft really has everything tightly integrated well. We rely heavily on our community to determine our development path, so please reach out to us when you do, and leave feedback! "I'd love to try this out eventually, joining a new team soon and perhaps I can pull it off there if/when pairing needs arise!"
#COSCREEN CRUNCHBASE WINDOWS#
Ultimately this helps in like the pair programming scenario you make above, but is a weakness in other situations: we are working on a model that will let you break all of the window locations apart, or relatively translate the position of another user's windows wherever you want. "With CoScreen, would "hey, can we check the logs real quick?" become as simple as the other peer clicking the window to add it to the session?"īasically yes, there is a tab that shows above your window.Īt the moment we have a shared context space, so your windows have a relative location that is based on the layout of the remote screen. No problem! It's actually a great conversation starter. "Thanks for taking the time to answer my bad question sincerely!" Our goal is to facilitate things like pair programming by fading into the background and just letting you continue with your normal workflow while not thinking about the tooling behind it. That being said it's going to be a great challenge to make this experience more transparent, and we are actively working on different scaling modes, the ability to move windows independent of remote users, and other concerns that we think will take it to the next level. It's a paradigm shift from video conferencing, and traditional screen sharing tools that I think has to be experienced to be understood.
Or you have a Android/iOS emulator that you want to immediately preview your work in.īasically you're working in a shared working space more analogous to what you would experience in the office. The remote user looks up some documentation, and immediately shares it with you. You can be discussing a piece of code, share vim in Alacritty, or iTerm. You see their shared cursor over your window that is translated into the adjusted coordinate space for that window. Then there is the friction of allowing sharing, asking for sharing, or even down to just knowing where the remote user's cursor is at.ĬoScreen eliminates all of that. We have bet a lot on the benefits of producing frictionless remote app-level sharing.Īt the moment you can share one application, or your entire desktop with other tools. This is honestly one of the biggest hurdles I think we have towards adoption. I think it's a really good question and not snarky at all.
0 kommentar(er)
