Hi everyone! We are Dragos and Thiago from GitDuck (<a href="https://gitduck.com" rel="nofollow">https://gitduck.com</a>). We are building GitDuck, a Zoom for developers with direct integration to the IDE so software developers can talk and collaborate in real-time.<p>It all started by accident, Dragos and I were working on something else, a screen recording tool and we started to use it internally to record short videos of our code. At first it was just for quick code reviews and to debug, but soon we realized how helpful it was to have a video explanation of the code. Kind of rubber duck debugging with video. ;)<p>After talking to almost 300 developers and learning that other people were facing similar collaboration issues we decided to focus 100% on building this tool. We are the first users and we use GitDuck internally for quick assistance, pair programming, code reviews or just discussing ideas.<p>It has the features you would expect in a video call tool — like audio, video chat and screen sharing, but the UX and the integrations were built exclusively for developers. You can easily share your code and do pair programming. We are building integrations for all the IDEs. This enables you to collaborate without screen sharing (so it's faster and and consumes less bandwidth), directly from your IDE and independently of the IDE that other people are using.<p>Whenever you join a GitDuck meeting, your IDE extension wakes up and allows you to share your code with the other meeting participants (or join the already shared code from other meeting participant). When your peers join your code, they can see and edit your files in real-time, similar to the Google Docs experience. At any given point you can also go to your peers position so you can see in which file and line they are.<p>Check a 1 min demo
(<a href="https://gitduck.com/watch/5f1808919552aefe64ce0751" rel="nofollow">https://gitduck.com/watch/5f1808919552aefe64ce0751</a>)<p>GitDuck currently has integrations to VS Code and VSCodium. In the next few days we are going to release the integrations to all JetBrains IDEs. Vim, Sublime and others coming after that.<p>One important aspect to mention is security. We are the first users of the service so we focus a lot on building something that we would trust to use ourselves. All the files shared from your IDE are always shared via peer-to-peer and are end-to-end encrypted. No piece of code never touches our servers, so we never have access to your code.<p>All calls are encrypted and p2p (if 4 or less participants). If 5 or more people join we switch to a cloud infrastructure in order to maintain the quality, but the media are always encrypted and we never have access to your calls. You can read more about it here (<a href="https://gitduck.com/security" rel="nofollow">https://gitduck.com/security</a>) and we are always open for your suggestions to improve.<p>We would love to hear your thoughts and feedback. What are your ideas about tools like this?<p>Thank you!
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.<p>I’ll give this a shot tomorrow with some friends and see how it goes!
How is this product "Zoom for Developers"? What makes GitDuck like a video conferencing platform which supports 100+ concurrent users?<p>To me "Zoom for x" implies video calling as a primary feature.
Definitely a step forward in sharing by allowing each person to use their own editor. Looking forward to the vim plugin.<p>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.<p>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!
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?
How is this better than Visual Studio (Code) Live Share [1]?<p>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.<p>[1]: <a href="https://visualstudio.microsoft.com/services/live-share/" rel="nofollow">https://visualstudio.microsoft.com/services/live-share/</a>
I get why you’re saying “Zoom for...”, but I see Zoom as a poorly designed, user hostile and anti-privacy platform. It’s good to see that your description also mentions security. But it doesn’t mention anything about the word “privacy” explicitly, and that’s a huge missed opportunity for any solution that claims to be a Zoom replacement or alternative.
For those searching for the pricing. Here you go:<p>Startup
Unlimited calls
Up to 20 people in a call
Unlimited rooms<p>$20 per team member / per month
I'd love to try it, but your terms of service seem to completely ignore GDPR.<p><a href="https://gitduck.com/terms" rel="nofollow">https://gitduck.com/terms</a><p><pre><code> 2. Communications
By creating an Account on our Service, you agree to subscribe to newsletters, marketing or promotional materials and other information we may send.
...
11. Analytics
We may use third party services (including Amplitude, Segment, Crisp and Google, and their respective affiliates) that collect, monitor and analyze this Log Data to provide analytics and other data to help us increase our Service’s functionality and to help us advertise our products and services. These third party service providers may use cookies, pixel tags, web beacons or other storage technology to collect and store Log Data or information from elsewhere on the internet. They have their own privacy policies addressing how they use Log Data and we do not have access to, nor control over, third parties’ use of cookies or other tracking technologies.</code></pre>
So most devs are on VSCode and they already have LiveShare which works pretty well.<p>Is the point of this for the non vscode crowd? Trying to understand what is the justification of paying for something like this.
I appreciated the copy of the landing page--my literal first question after 'what is this?' was why would I use this when slack video and live share has been fine...it's still a tough value proposition but I'll certainly give it a spin and really would love to see a dev-built company like yours suceed!
This is really cool.<p>A couple of thoughts:<p>The screen share cannot be fullscreened(?), which makes it hard to see fine details.<p>The pair-programming code sharing didn't work VSCode to Pycharm (Or my coworker didn't get the plugin configured correctly in Pycharm).<p>Overall though, GitDuck seems like a great tool.
Site and demo won't load for me.<p>The naming and references to 'Zoom' are odd. Instead of "Zoom for developers" maybe explain exactly what that means? Is is screen sharing and group meetings?<p>When you compare yourself to zoom I immediately set the bar that the usability/performance/security/etc. must at least be to their level.
This name violates the git trademark policy: <a href="https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw@sigill.intra.peff.net/" rel="nofollow">https://public-inbox.org/git/20170202022655.2jwvudhvo4hmueaw...</a><p>I do like the “duck” part of it though!
Sounds neat, but I think your name runs afoul of Git's trademark; see <a href="https://git-scm.com/trademark" rel="nofollow">https://git-scm.com/trademark</a>
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.
If this project takes off, I see a lot of people mis-typing gitdick instead. Probably should either look at changing the name or at least also registering gitdick.com pre-emptively
It "is zoom" or it "isn't zoom"? This was confusing to me. Perhaps you are directly integrating with zoom so actually it is zoom. Or else you have some sort of clone.
Can I ask, why did you launch this product without all the major IDEs being supported? I use webstorm, but the thought that it won't be supported for a few days means I may just forget about the product unless I am reminded again..