31–40 of 113 posts
How is this better than Visual Studio (Code) Live Share [1]? Adding a third party dependency for code-sharing seems like a non-starter for large enterprise companies which already have a hard enough time with the first party offering. [1]: https://visualstudio.microsoft.com/services/live-share/
I don't use VS Code, and I'm not going to switch IDEs for code sharing. I am more likely to try GitDuck since my colleagues who use VS Code can also use it.
I've never thought much about pair programming within the same file, seems like a super interesting concept. Obviously co-editing e.g. google docs makes sense, but there's no user-facing concept of validity here. How does saving work, is the idea that someone codes while someone watches? This already causes all sorts of fun with collisions in git, how do people work around that locally with things like hot reloading?
The way it works is that you are sharing your local files to the other people and when they edit the file, all the changes are being applied to your file. So in the end you are the one saving all the changes and making the commits. You can be working in parallel in different files or just following around. It really depends on what you are trying to achieve. One cool thing to try with GD is mob programming. :)
I’ll give this a shot tomorrow with some friends and see how it goes!
For a Linux user, you can already build such a system yourself quite trivially by installing an x11vnc server on your host, setting up a SSH tunnel to a remote server which forwards the host's VNC port, and sharing SSH credentials with your colleagues who can use a VNC client to access your screen from Linux, Windows or Mac.
I was a big fan of Floobits a few years back. Tuple and Screen.so are great, but we have devs split between VSCode, vim 8, and Neovim, with different configurations. I would definitely pay for cross-editor collaboration that works. I’ll give this a shot tomorrow with some friends and see how it goes!
Earlier quoted context omitted.
The way it works is that you are sharing your local files to the other people and when they edit the file, all the changes are being applied to your file. So in the end you are the one saving all the changes and making the commits. You can be working in parallel in different files or just following around. It really depends on what you are trying to achieve. One cool thing to try with GD is mob programming. :)
Very cool! .. so does that also mean the remote worker can't / doesn't save? Also are the changes reflected locally for both users for e.g. testing / compiling or do you rely on compute of the remote host like VNC? How about tracking changes?
Tracking changes is coming soon! This is super needed.
We are going to add soon better tools to manage (and share) the local server. So you as a guest can edit, save and see how this is impacts the local server of the host.
I find myself also sharing consoles too, I'd like to see this extended to terminal sessions, perhaps the session could be rendered in other people's editors? Kind of like a live asciinema.
I'd love to try this at work, unfortunately streaming Corp's code through an unapproved 3rd party service is a no-go. This would've been really useful in college. Hope this catches on!
How is this better than Visual Studio (Code) Live Share [1]? Adding a third party dependency for code-sharing seems like a non-starter for large enterprise companies which already have a hard enough time with the first party offering. [1]: https://visualstudio.microsoft.com/services/live-share/
The browser version of live code did work, but no. I'm not doing that.
I used to use zoom for pair programming. It got banned because, as you said, Large Enterprise Company. Microsoft lobbied them with "trust us: the company behind skype knows how to write secure software. force uninstall zoom on all your employee computers if you know what's good for you". Microsoft corporate sales are wizards.
Since zoom bombing was a thing and we couldn't be trusted to set our own passwords, I also tried using Microsoft Teams to pair program. It was absolutely unusable (e.g. if you type the keyyyyyyyssssss willlll stickkkkk).
GitDuck is probably lovely. It's a shame neither of us can use it.
How is this better than Visual Studio (Code) Live Share [1]? Adding a third party dependency for code-sharing seems like a non-starter for large enterprise companies which already have a hard enough time with the first party offering. [1]: https://visualstudio.microsoft.com/services/live-share/