4 ms·
Definitely a step forward in sharing by allowing each person to use their own editor. Looking forward to the vim plugin. I find myself also sharing consoles to
by tucif 6y ago
Definitely a step forward in sharing by allowing each person to use their own editor. Looking forward to the vim plugin.
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!
- borisandcrispin 6y agoTerminal sharing is super important and we will work on it soon. This is one of the things that we need the most when we use GD internally. Connections are P2P btw, no code touches our servers. But yeah, I understand this is not enough to get approval.
- Aperocky 6y agoAs someone who's most used editor by far is vim (can't escape IDE when writing java), I'm happy that you're doing this. However I feel like your market may be more geared towards interviewing/learning, I don't see how in my work environment that we'll ever need this.
- alfix 6y agoIs this a variant of the dropbox joke?
- drag0s 6y agoGitDuck founder here. The use-case you’re describing is definitely in our roadmap! Your concerns are totally understandable and we’re more than happy to discuss how to get GitDuck approved on your Corp. Security is one of our top priorities! [1] As Thiago said, code is shared on a P2P e2e encrypted way (code never visits our server) and we can always discuss on-prem options (100% hosted in your infra) so no data at all leaves your network and you can control all inbound/outbound traffic. Feel free reach out if you have any other question or concern! [1] https://gitduck.com/security https://gitduck.com/security
- manx 6y agoFor terminal sharing I highly recommend https://tmate.io/ https://tmate.io/