The document’s journey from file to editing: processing 1,000 pages and not dying
summary
Explains how a modern web text editor processes a document from the file stage to interactive editing, describing the technologies used (browser-based editor internals and related web technologies). Compares implementation choices and performance techniques, and specifically outlines why Yandex Docs is faster than Google Docs.
AI-written summary · about
chapters (21)
- 0:00Document’s journey to editing
- 2:51Third-party issues
- 4:17Team goals principles
- 6:27DocX XML structure
- 8:12Custom data model
- 10:17Data transformation server
- 12:02Sync problems
- 14:07Operational Transformation vs CRDT
- 16:56CRDT algorithm R&D
- 18:02Document display gap
- 20:11HTML rendering issues
- 21:13Empty page layout
- 23:22Model to rendering
- 25:45Typography calculation
- 27:32Math display model
- 28:56User input interaction
- 30:22Rendering optimization
- 31:47Test results
- 34:13Performance limits
- 35:35Solution achievements
- 37:42Conclusion
related talks
46mHow We Built a Web Document Editor
32mDeveloping a Document Editor
37mBuilding a Collaborative Text Editor
41mMarkdownEditor: The Next Step in Working with Text
04h 48mBuilding Our Own Text Editor
57mDeveloping a Rich Text Editor: Problems and Solutions
23mBuilding a real-time collaborative editor with Phoenix
32mBuild a Google Docs clone with CKEditor 5 & Vue.js Solution LIVE