gobby

https://github.com/ONLYOFFICE https://github.com/dream-num/univer https://github.com/ether/etherpad-lite https://github.com/firebase/firepad https://github.com/prosemirror https://github.com/CollaboraOnline/online https://github.com/hedgedoc/hedgedoc https://github.com/gobby/gobby

Thanks for the article, interesting read! How well does this approach scale to high-concurrency situations? The more active participants there are, the more often you'd be rejecting client changes and ask them to rebase, causing extra round-trips. It sounds like when a critical number of participants is reached, you'll create change requests more quickly than you can handle them. If each participant has a latency of 100ms to your server, and say you have 10 participants making 2 changes per second each, will you experience some sort of congestion? On a similar note, what happens if you have two active clients, one with say 100ms latency and another with 500ms? If the 100ms client will be typing continously with 4 characters per second, the changes of the 500ms client won't get through until the 100ms one stops typing, right? I realize the