Live data from Hacker News

Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

news.ycombinator.com

91–100 of 113 posts

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#92
post #88

Earlier quoted context omitted.

I don't understand why slack is worth billions when IRC has been around for decades.

because slack is a product and IRC is a protocol? what is the actual irc-based alternative to slack?

Probably IRCCloud - Slack's UX is definitely more usable for most.

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#93
post #13

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/

Seems very odd to assume that every single engineer is using VS Code, thus making this a third part dependency.

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#94
post #22

Earlier quoted context omitted.

nobody's mentioned them so i'll toss them in here - https://tuple.app/ is also focused on the pair programming problem. I don't believe they have IDE integration, but like others have said, Tuple + Live Share would be a competitor to GitDuck. Glad to see more attempts at the space though!

Can't say I've ever encountered a startup selling an "Enterprise" plan but their software also ONLY supporting Mac. Are there enterprises where they use Mac as default over Windows / Linux?

Well, anecdata I suppose, but I know plenty of startups where developers are exclusively mac. Not the showstopper you might imagine.

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#95
post #93
post #13

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/

Seems very odd to assume that every single engineer is using VS Code, thus making this a third part dependency.

Honestly it's not a ridiculous assumption. Right now, in web-startup-land, it's a very high percentage. Exceptions would be the unix tool users - vim/emacs - and I suppose they would be expected to temporarily embrace VSCode for the sharing session.

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#96
post #34

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 don't know if you're joking, but I'm in the habit of using ZeroTier+VNC.

that works quite well, especially between macOSes, but only down to 1Mbyte/s bandwidth, if u r sharing a FullHD.

below that bandwidth, the latency is getting into the annoyingly high territory. and of course I'm taking about using it in approved quality mode.

it nicely handles HiDPI resolutions too, but unfortunately the built-in macOS vnc viewer can only scale down the screen, not up.

another issue is that zerotier doesn't work in China, but that's more of a social than technical issue unfortunately...

what I found is that Tuple.app makes a more useful compromise between latency and image quality. on low bandwidth your image might look like a balls of random pixels on first glance, but on a second look you can surprisingly still read it. meanwhile latency remains below 0.5s, so you can keep thinking together with your pairing partner.

screen.so over low bandwidth keeps the image quality significantly higher than just-above-unreadable, but then you are experiencing jittery 1-6 second screen update frequency.

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#98

I have no idea why it’s called GitDuck. Code != Git?

It's because of the rubber duck methodology and in the early days we thought it would be cool to have a command `git duck` that starts a video to explain a commit.

I'll be blunt here, but I really do mean this in the spirit of constructive criticism: I hate the name. It's not related to Git in any meaningful way (why not "VimDuck" or "ZshDuck"?), and at first glance I'd assumed it had something to do with Cyberduck. Also, it doesn't exactly roll off the tongue: "hey, wanna hop on a Zoom?" flows better than "hey, wanna GitDuck?" Finally, the name pretty much limits it to only developers. Zoom was in a great place to capitalize on schools that were moving to remote classes, but "Zoom" doesn't really carry any semantic baggage. It would be awkward to explain to my boss why I wanted our company to your product for a business meeting, even if it's the perfect tool for it ("what's a git? What's it have to do with ducks?").

Re: Launch HN: GitDuck (YC S20) – Zoom for developers with real-time code sharing

#100

I'd love to try it, but your terms of service seem to completely ignore GDPR. https://gitduck.com/terms 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, moni…

Gotta love a legislation which makes it much harder for startups while favoring the fully lawyered-up big tech.

Never forget what the GDPR fan boys claimed about this legislation being some kind of Big Tech "killer", and now go and look at Big Tech stock prices.

Post reply on HN