Live data from Hacker News

Viewing profile — antics

antics

HN member
Joined
Fri, Aug 13, 2010, 8:09 PM UTC
HN karma
4,108
Public activity
501 items

About antics

clemmer.alexander@gmail.com alex@moment.dev

Recent public activity

  1. comment
    Comment #47589014

    So on the one hand you have a direct statement from the source that the cause of this incident is humans. On the other hand, while we all agree there is no specific evidence that A…

  2. comment
    Comment #47583577

    > I'm not sure why people are so quick to discount [AI] as a potential source of the issue. Because (per the link above) the CEO said that (1) it was their fault, and (2) it had no…

  3. comment
    Comment #47582603

    The CEO says it's not: https://x.com/JustJake/status/2038799619640250864 A lot of people are confident in enough in their ability to spot AI infra that they are willing to dismiss …

  4. comment
    Comment #47447757

    > It feels a little weird to put 100 hours into something that won't be noticed by its absence. Exactly no one will think, "man this dithering is stable as shit. total magic going …

  5. comment
    Comment #47442415

    lol ok we can talk and record it. I want to make it clear that this is NOT a debate, though. I actually want to be convinced!

  6. comment
    Comment #47432049

    But Kevin, prosemirror-collab does give me offline editing. I use it literally every day, entirely without issue. I write offline on different devices, and whenever I come online, …

  7. comment
    Comment #47429332

    I run a VC-funded startup. We fund the extremely high-quality OSS `react-prosemirror` project at > $10k a year. I really, really think you should too. Here was our thinking: - Chea…

  8. comment
    Comment #47427426

    But Kevin, you never really answered the question of the article. Unless I need a truly-masterless p2p topology, why would I do all this stuff, including throw away editor intent a…

  9. comment
    Comment #47427350

    The magic of CRDTs does not prevent this. They are in exactly the same boat as OT, prosemirror-collab and prosemirror-collab-commit. It can't be prevented. The problem is worse wit…

  10. comment
    Comment #47423336

    I do not know how to say this another way. No. Nothing in this article was created, edited, outlined, pre-drafted, suggested, or in any other way influenced by AI. AI did not write…

  11. comment
    Comment #47422662

    Actually, I think I agree with most of this... except the part where you think it's not clear-cut, ha ha. I meant that not as a comparison between OT and CRDTs, but as a comparison…

  12. comment
    Comment #47422635

    Ok Marijn I understand. I'm sorry I caused you an inconvenience. Of course, I know that implementing server-side prosemirror-collab is not entirely without problems (since we have …

  13. comment
    Comment #47422610

    Just to be extremely clear: we pay for a lot of OSS software. We pay one individual project more than $10,000 a year. We would have paid for Yjs too, if we thought it was a good us…

  14. comment
    Comment #47422547

    Hi Joseph! Good to see you here. Sorry, I see why this was confusing. What I'm saying is that because users perceive the results of OT, CRDTs, prosemirror-collab, etc . as data cor…

  15. comment
    Comment #47422495

    Thanks Nick. I am aware. The blog post directly links to the PR you merged some days ago that (as I understand it) kicks off the effort. I also mention specifically I know you're w…

  16. comment
    Comment #47422490

    Just tying up loose ends here, in this other comment I suggest that Kevin and I are not on the same page about the point I was making in the article: https://news.ycombinator.com/i…

  17. comment
    Comment #47422455

    Hi Kevin, author here, are you sure we are on the same page about what I'm saying in this article? For example, the debugging section is NOT about debugging problems inside Yjs, it…

  18. comment
    Comment #47405233

    So, we are basically making two points. First, the fact that Yjs bindings, by design (for ~6 years), replace the entire document, does in my opinion, indicate a fundamental misunde…

  19. comment
    Comment #47404874

    I know it seems that way, but it's actually not 80% of the way to a CRDT because rich text CRDTs are an open research problem. Yjs instead models the document as an XML tree and th…

  20. comment
    Comment #47404654

    It might fix the replace-everything bug. It definitely does not fix any of the other issues I mentioned. Even just taking the permissions problem: Yjs is built for a truly p2p topo…

  21. comment
    Comment #47404615

    Hi Matt! Good to see you here. For those who don't know, Matt also wrote a blog about how to do ProseMirror sync without CRDTs or OT here: https://mattweidner.com/2025/05/21/text-w…

  22. comment
    Comment #47404589

    To be clear, we ARE arguing CRDTs needlessly complex for the centralized server use case. What I am describing in the "delete and replace all on every keystroke" problem is the poi…

  23. comment
    Comment #47404526

    First of all, thanks for chiming in! I wish someone would collect stuff like this and write it down in some sort of "oral history of collab editing." Second of all, I actually thin…

  24. comment
    Comment #47404296

    Author here, just chiming in to say that Matt has an actual PhD on the subject so rather than explain it worse, I will just let him say the probably-actually-correct thing here.

  25. comment
    Comment #47404276

    Great question. Matt has a comment about this here, and he has an actual PhD on the subject! So rather than doing a worse job explaining I will leave it to him to explain: https://…