5 ms·
It’s hard enough getting your own code to run and work correctly. When would this be a useful development paradigm?
by vlovich123 6y ago
It’s hard enough getting your own code to run and work correctly. When would this be a useful development paradigm?
- topicseed 6y agoRealtime collaboration on documents (e.g. source code, rich text editing, etc).
- ickyforce 6y agoWhen I edit code it's broken most of the time. It wouldn't make sense to collaboratively break it in various parts for other people...
- dkersten 6y agoI have done remote pair programming many times though and in that case it’s perfectly ok, because you’re communicating with the other person/people and can let each other know if you will break something. For that use case, I can see this being very useful.
- IggleSniggle 6y agoWhile you could do real-time collaboration on code edits with this tool (and I've done that with some success via pair coding, where you commit them to git after your shared edits are complete), this tool isn't strictly about code. It's about any shared content at all. Think google docs, but for any data, with offline/online sync. The offline/online sync might not be great for simultaneous edits, but in a shared "project" of say, field research data, the combination offline/online sync and soft-realtime shared documents at any hierarchy level layer is a nice "don't need to think about it generally" approach. I'm not sure which kind of CRDT these are, but since all edits are part of history, as in git, you're not going to lose history if someone DOES inadvertently stomp on someone else's edits.
- vlovich123 6y agoI understand how it's useful for documents. I don't believe source code is anything like a document and thus that mental model doesn't feel useful.
- kohtatsu 6y agoThis is a library, not a tool.
- skybrian 6y agoCRDT's and operational transforms are most useful for live, online editing. Each client sees a nearly up-to-date version of the document and any differences due to network lag are relatively small. The idea is that normally each user will see other users' edits as they happen. They are trying to cooperate, not stomp on each other's edits. So long as the merge is reasonably intuitive, it can be fixed manually if it's not exactly what the authors wanted. CRDT's aren't very good for writing code asynchronously, since you probably want each version to compile and pass tests, and sometimes do code review as well. Git works better for that. But they could be sort-of-okay for pair programming, though it might be an overly-complicated solution and better to use some kind of remote desktop.