Hacker News new | ask | show | jobs
by haroldadmin 29 days ago
ProseMirror is an excellent project, but it’s always been a bit awkward using it directly in React. I remember that NYT had to rewrite the renderer to make it work for their use-case.

I wonder how Wordgard compares in this aspect!
3 comments
exceptione 29 days ago
For people who have dealt with react, this part might give some insight into that topic (https://wordgard.net/docs/prosemirror/#h-transactions-and-ch...)? Nevertheless, it would be good if this could be addressed in the docs.

I am not sure if this makes things easier for react interop, but this piece might be of interest too:

  > One of the biggest mistake blunders in ProseMirror is that the editor view does not get access to the transaction objects when updating, just the state. Wordgard does not repeat this mistake, and makes updates take transactions, not just a new state.

  > This means that things like the DOM update logic and UI plugins can precisely observe what happened, and handle changes in a efficient and more effective way. The weird unexpected DOM redraws that are still a thing in ProseMirror should not occur. Only the precise DOM structure affected by the new transactions will be updated.
Anyways, it is great to see Merijn still going strong with his free work. Anyone needing interactive rich text on the web won't find anything better than his brain childs.
link
tefkah 29 days ago
The people developing that left NYT and spun it out into a separate (really great!) project https://github.com/handlewithcarecollective/react-prosemirro...

They are also working on a collaborative editing suite for ProseMirror as an alternative to TipTap https://pitter-patter.dev/

link
alserio 29 days ago
That's due to the React constraints, though
link
yard2010 29 days ago
Can you please elaborate? What constraints exactly?
link
alserio 29 days ago
React expects to own the DOM and that state is managed by pure functions. There are good reasons for this, but the consequences are that it's restricting how the web platform works and when something does not agree with it weird things can happen. Is it bad? Sometimes. Is it the rest of the Web fault? I don't believe so. If you are using React you are largely constraining yourself to work in the React model, not in the Web model. That might be fine, but it might also not be.
link