May 5, 2026
Ctrl+Alt+Delight
Collaborative Editing in CodeMirror
Code editor update goes "boring" and fans are calling its creator a legend
TLDR: CodeMirror’s creator says the best way to let people edit together is the less flashy, centrally managed option—not the internet-freedom fantasy. Commenters barely argued and mostly turned the thread into a Marijn appreciation club, calling him a hero, the GOAT, and outright blessed.
A software tool most people have never heard of somehow produced the most wholesome nerd pile-on of the day. In a new post about the next version of CodeMirror—a popular code editor system used behind the scenes in apps and websites—creator Marijn Haverbeke basically says: yes, he explored the flashy ideas for people editing the same file together, and no, he didn’t pick the sexy one. Instead of chasing a wild fully peer-to-peer dream, he chose a plain, coordinated server-based approach because it’s simpler, easier to manage, and better suited for the real web. In other words: the big reveal is intentionally “boring.”
And the comments? Absolutely not boring. The strongest reaction wasn’t outrage over the design choice—it was a near-immediate coronation ceremony for Marijn himself. One fan gushed that his code is “really easy to read” and started name-dropping his parser project Lezer and even Eloquent JavaScript like a proud stan making a fancam. Another commenter went full myth-making: “Marijn Haverbeke and Fabrice Bellard are my heroes.” Then came the simpler, louder endorsements: “Goat.” “blessed.”
The drama here is delightfully low-stakes: not a brutal flame war, but a clash between cool futuristic ideals and practical grown-up engineering. The funniest bit may be that a post openly selling a “negative result” somehow turned into a community lovefest. Even the driest interjection—“(2020)”—lands like a deadpan meme, the comments equivalent of someone barging into a party just to check the timestamp.
Key Points
- •The article explains the design of the upcoming CodeMirror version's document-change data structure and built-in collaborative editing feature.
- •The chosen design is a centralized, non-distributed operational transformation approach rather than a distributed collaboration model.
- •The article distinguishes distributed peer-to-peer collaboration problems from the server-coordinated model used by most web editors.
- •It states that distributed systems add complexity such as storing full history, discovering peers, and maintaining connections.
- •The post outlines how a centralized OT system manages unsent local changes, server acceptance or rejection, and transformation of local and remote edits.