As a company, we @moment_dev have a single ambition: to make it possible to run your entire business out of a Markdown file.

Anyway, If you are building something like this, we'd love to hear from you! I think we will all sort this out quicker if we talk about what we're doing publicly.

Third off: although peculiar to our situation, because our documents are both collaborative, and also, Markdown files on disk. This means you can actually use stuff like `copilot` or `claude`, or `amp`. You can see where we ended up here: www.loom.com/share/f70bf5...

opus-4.5 has very helpfully offered improvements to the Gettysburg Address

Second off, and very relatedly: it is VASTLY EASIER to inspect two `.md` files and compute a "suggested change" from them, than it is to build a harness that turns bad patch files and CRDT ops into good ones. The algorithm we wrote is in the blog post. (Not perfect; just easier)

Our approach is maybe the opposite of what you'd expect. First off, the models are very bad at generating `.patch` files or CRDT ops. They don't do line numbers well! But they are good at editing `.md` files. So it is VERY IMPORTANT that your on-disk format is `.md` (or similar)

Lee Byron (OpenAI) - Teaching Models to Collaborate YouTube video by Local-First Conf

But, we couldn't actually find anyone that does this, and the reason seems to be that it's super hard. Lee Byron @ OpenAI even gave a talk about this: https://
youtube.com/watch?v=kQSfXSliBzU
But Google Docs, Coda, etc., all actually do something else. Cursor does do this, but only for plaintext.

opus-4.5 collaboratively editing a document with human users.

When we set out to do this, obviously, we wanted the agent to look/feel like a normal collaborator. For our product, we wanted a bunch of live-collab between human users AND ALSO, some number of AI users.

Collaborative editing with AI is really, really hard / Moment devlog

(Here is a longer blog post about it, but I'll continue with the Cliff's Notes version in-thread) www.moment.dev/blog/collab-...

🧵 Collab editing with AI is really, really hard.

Some day I will fully internalize that nothing in text editing is ever truly solved. Like alcoholism, it's a problem that never really goes away. A tumble-dryer that exclusively outputs mismatched socks/other off-by-one errors.

More spite-driven version control UI, this time for git push.

Increasingly annoyed with modern version control UI, I have spent a bunch of time this holiday break playing around with a new, "bladed" UI for exploring commits, branches, and commit history.

Also lol oops meant to tweet this from Moment bsky account

Segment of blog post explaining that React's monolithic render loop is generally NOT at the root of perf problems???

Surprise 3: React's monolithic render pass is surprisingly generally not in the way of achieving 60fps???

Segment of blog post explaining that even collaboration libraries generally do not appear to be designed for 60fps.

Surprise 2: That includes almost all available text collaboration libraries??

Segment of the blog post explaining how almost no libraries appear to be built for 60fps.

Surprise 1: almost no libraries are really built to achieve 60fps. :(

Introducing the Moment devlog / Moment devlog

Changelog 0004: Underappreciated aspects of text editor performance. 🧵 www.moment.dev/blog/changel...

Ok ok, it's a Yaak-style API client. But, you know, without all the features.

The idea is: type in a URL, specify headers, params, and a body, and click the Send button. You receive a response. Or, you can paste a cURL command to autopopulate all of these things.

We're starting a changelog! :) bsky.app/profile/mome...

Introducing the Moment devlog / Moment devlog

You can kind of get a sense of what we're going to talk about from our somewhat-bombastically-titled blog post, Lies I Was Told About Collaborative Editing: www.moment.dev/blog/lies-i-... Mostly this gets at how hard collab editing is in the offline case.

Now that launching true collab editing is imminent, we are starting to talk about the reality of building a realtime system like this. It has been... an interesting ride.

When we started to build collaborative text editing into our product, we had a very, *very* hard time getting practical advice about it. This talk is going to be just all the stuff we wish we'd known when we started.

Every time you say this something terrible happens.

Also, your recommendation is right up my alley and I am excited to read it next. I think it's probably not about the exact same thing but, e.g., I really enjoyed Lawrence Wright's The Looming Tower and the movie Reality (which was panned but I think is very good).

Yep I have been thinking about this for decades. Many years ago I thought it captured something interesting and modern about masculinity, youth, and fame. Now it is my own personal memento mori, a pebble in the shoe of life that randomly appears to remind me: you are ancient

THE WAY WE LIVE NOW: 3-9-03: ENCOUNTER; Loves Microsoft, Hates America (Published 2003) Adam Davidson article on Fadi, young, unemployed computer programmer who lives with his parents in Amman, Jordan; Fadi has two conflicting dreams, one to be suicide bomber and another to work for Micr...

This NYT article about a man who wanted to wage Jihad against America, and also work as a programmer at Microsoft: www.nytimes.com/2003/03/09/m...

What about if hypothetically you were a fan of complaining

if you die in canada you die in real life