Hacker News new | ask | show | jobs
by kyleashipley 2129 days ago
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!

1 comments

Let me know how it goes!
Tried it out for a couple hours today! A quick experience report:

  - Collaborative editing was very solid, even with one of us using vim extensions and the other one not. (This has caused me some pain in Screen.so in particular.)
  - The leader/follower model was slightly unintuitive at times. I vaguely recall Floobits allowing either participant to e.g. create new files, but in GitDuck the leader has to share them to the workspace for them to become editable. (I might also be misremembering this from the Floobits days, but it was slightly confusing.)
  - Similar to ^ - when I was not leading, I couldn't summon the leader into a file I was editing, so I had to tell him when I was switching files. IIRC Floobits let you take yourself in/out of follow mode, even as the leader, so you would be automatically summoned when the other person switched files.
  - Looking forward to terminal support - glad that's on your roadmap :)
  - Our team is 50/50 between vim and VSCode right now, so we're looking forward to vim8/neovim support to really feel the power compared to Screen.so and Tuple.
Overall, had a surprisingly smooth experience for Day 2. Congrats on the launch and looking forward to future updates!