ghProTip

7 ms·

1. 1.▲
   by ghProTip 6mo ago

   > Maybe even recorded, if people are interested in that. I would be. IIRC you interviewed the Yjs creator years ago in a YT video I watched? This post has been fun spicey discourse not withstanding. It's not often a lot of the peopl
2. 2.▲
   by ghProTip 6mo ago

   Heya, cheers. I'm actually intimately familiar with the node splitting issue. I've created y-prosemirror backends(complete with edit history, snapshots, etc) and "rewrote" y-prosemirror in TypeScript heavily refactoring
3. 3.▲
   by ghProTip 6mo ago

   The algorithm in prosemirror-collab-commit is inspired by Google Wave, and implemented as a slight tweak to the prosemirror-collab system. The tweak is in the name. I'm not sure about classical OT, and it's been a really long time
4. 4.▲
   by ghProTip 6mo ago

   Cheers for plugging prosemirror-collab-commit! Nice to see it's getting used more.
5. 5.▲
   by ghProTip 6mo ago

   Couldn't agree more with the gist of the argument, especially in the context of ProseMirror. That's why I created prosemirror-collab-commit.
6. 6.▲
   by ghProTip 1y ago

   Created this tiny JavaScript project and published on npm for when you just can't be arsed remembering/learning JQ: https://www.npmjs.com/package/jsling . Not shilling it so much as saying.. IMHO, for a lot o
7. 7.▲
   by ghProTip 2y ago

   Nice! I used TipTap on top of ProseMirror(and ProseMirror.Net) with stepwisehq.com . Most React prosemirror-based editors were making the same mistake a couple years ago; re-rendering everything on each keystroke. Particularly the tool bars