Lita 조원경

@fat also `jj` support 🙏🙏🙏🙏

Coming soon to merge conflicts in diffs[dot]com. Dynamic roll ups for unmodified code allow you to present only the conflicting hunks (while still allowing for dynamic expansion of rest of file).

@fat omfg, more code for me to delete!!!

@pierrecomputer This is the feature that caused me the switch. Working out some workarounds. Looking forward to jj conflict marker support 🙏🙏🙏🙏

New update to diffs[dot]com today includes a ui component for merge conflicts try it out!

Ok. For the last, like, 15 years, I've constantly been told that CRDTs (and Yjs in particular) solve collaborative text editing. Both the offline and live-collab cases. After an excruciatingly painful evaluation, I argue not only is this completely false, they're generally not appropriate for production-grade editors... at all. Yeah, I know: everyone uses Yjs, so the problem must be us. Right? That's what I thought too. Well, did you know that on every single collaborative keystroke, Yjs will REPLACE YOUR ENTIRE DOCUMENT? (See this GitHub issue: github.com/yjs/y-prosemir…) Did you know that this is BY DESIGN? (See this discussion on the ProseMirror boards: discuss.prosemirror.net/t/offline-peer…) Did you know that this breaks, like, every editor plugin? (See the ProseMirror author's commentary here: discuss.prosemirror.net/t/offline-peer…) I am not trying to bag on anyone, but to me this kind of mistake belies a fundamental misunderstanding of what text editors need to perform well, in any situation, let alone a collaborative one. Anyway, learn from my pain. I wrote a somewhat long-form article about all the other challenges we ran into with CRDTs on our blog: moment.dev/blog/lies-i-wa…

We wrote about our live collaboration solution and why a centralized server approach worked for us vs. CRDTs. If you are interested in collaborative editing, this is a must read!

@lenadroid HIIIii! Me!! I’m the problem it’s me!

If you're a techie from Seattle or SF who is also a Swiftie, speak now ❤️‍🔥 This is me trying to make sure you don't miss the 1 great thing that is coming up.

@fat ommmgg we are so honored!!😭 so excited to rip out our hand rolled prosemirror plugin.

@litacho yaa i built for you!

Merge conflict ux is coming to diffs[dot]com. Below is a quick side by side of syntax highlighting using our diffs library vs. monaco (vscode). Diffs[dot]com leverages a unique multi-pass rendering architecture so that syntax highlighting is correct across conflicting hunks. We do this using web workers and then stitch the results into a single file view. The result is proper syntax highlighting in all situations (unlike monaco who on the right is unable to correctly tokenize the "incoming changes").

We have been working hard to launch our take on collaborative editing, as it looks like it is in the new agent world for developers. We believe it looks multiplayer, with seamless integration with git (secretly it’s a mix of jj and git!) and live collaborative editing. We would love for you to try it out and hear your thoughts!

github, this is bullshit

Working with agents reminds me of working with 3D renders. You set a bunch of parameters and input data (model files, light positions and settings, shader files/code, point files for environments, etc., etc.) and send it off (in my line of work, it was sending it off to a render farm) and come back the next day and see what happened.

We're hiring a senior PM - does this sound like you? Here in @GoogleLabs we're leaning hard into a "continuous AI" future - a fluid cycle of ideating, building, monitoring, and iterating. One of my teams focuses on AI coding, and we're making this future real! We're looking for a senior PM who is excited about enabling a next generation of builders, has technical experience themselves, and is ready to build in an AI-native way. Pls share with folks you think would be great! google.com/about/careers/…

Moment is Google docs, but for markdown, with a git backend.

@threepointone @samuelcolvin @github @NotionHQ @southpolesteve We did! The first version was PartyKit and Durable Objects. @hausdorff_space wrote about it in moment.dev/blog/durable-o… We have now moved onto docs.reboot.dev and are super happy with the results. Love for you to give it a try and provide feedback.

@samuelcolvin @github @NotionHQ @southpolesteve yeah I could absolutely build this with partykit. was about to stat it, but I'm stepping out for a gig. tomorrow if I remember!

I find myself wanting a way to share and collaborate on markdown documents. @github isn't quite right - committing is too heavy, no simultaneous editing, web UI for review and editing isn't easy enough. @NotionHQ isn't quite right - hard to write locally (e.g. claude to edit) and sync easily, editing experience is more annoying than pure markdown. What I want is hosted markdown collaboration that easily let's me edit a file locally, and commits to github with an AI generated commit message regularly. Anyone know of such a tool?

excited to share the next iteration of what been building in the last few months.

I missed this at the time, sorry. Yes, this is what we do @samuelcolvin at @moment_dev. The product is basically a Notion-like workspace (live collab, tables, buttons that do things) but (1) it's also plain-old Markdown files, living in git repositories, on your local disk, and (2) it's programmable (because markdown) and therefore natively amenable to use with `claude`. Here, for example, are two templates claude pretty much one-shotted. An NES emulator with living memory space visualization: and a dashboard for our team's live PRs:

"I CAN'T BELIEVE MY EYES." 😳 Dual moguls madness as Nick Page skis out of the course for a DNF while his opponent, Ikuma Horishima, barely stays in control and skis over the line BACKWARDS for the win.

@isaacinthesky Stupid autocomplete. Codex.. not codes

@isaacinthesky Codes 5.3 is useable if you don’t mind going away for a long time. But if you wait to pair with it, it’s not that good.

dont really get how people use codex day to day? i find it pretty unusable compared to 4.6