How Collaborative Text Editors Don't Break
Today I dive into CRDTs, the data structures that make collaborative editing possible, hope you enjoy and let me know in the comments what you want to see next Btw, Im currently building SaaS for event tracking, if you’re interested, you can join the waitlist here: https://eventraze.com/ Links: ⬛ X (Twitter): https://x.com/pawelcodestuff 🟨 buymeacoffee: https://buymeacoffee.com/pawelcodestuff Timestamps: 00:00 The collaborative editing problem 00:31 Why basic sync doesn't work 02:33 Operational Transformation 03:14 CRDTs - conflicts impossible by design 03:44 Unique IDs, origin & origin-right (how Yjs works) 06:24 Tombstones & Local-First Software
▶︎
Building a collaborative text editor with WebRTC and CRDTs
▶︎
Why Elasticsearch Is So Fast
▶︎
the true reason C++ always wins
▶︎
Redis will finally make sense after this video
▶︎
Why is rendering text so complicated?
▶︎
It finally happened
▶︎
Why Tech CEOs Are Quietly Cancelling Their AI Plans
▶︎
Dear Game Developers, Stop Messing This Up!
▶︎
The paper scale system is broken.
▶︎
Most Devs Get API Authentication Wrong ?
▶︎
3 Databases Built for Specific Problems
▶︎
You don't hate BMW enough
▶︎
The Code Inside Everything (That Gets Zero Credit)
▶︎
Scaling Up the Full Scroll Dial - High Resolution Scrolling Device
▶︎
Three CSS patterns I use in every project
▶︎
Git Will Finally Make Sense After This
▶︎
500 million voxels/sec - Voxel engine optimizations
▶︎
The Game You Can't Fail
▶︎
Distributed Transactions Explained: 2 Phase Commit vs Saga Pattern
▶︎