Hacker News Reader

Comment by strogonoff | Hacker News Reader

This seems to be built on top of the venerable ProseMirror.

Had developed something slightly similar (for now primarily used in-house and API is somewhat clunky and unstable): essentially, a wrapper around ProseMirror that makes it easy to use in React, and introduces an additional abstraction that combines schema features and related editor plugins. Thought someone can make it better, and maybe this is that project.

Tangentially, a cool thing would be to unite ProseMirror with Automerge. That’d enable some killer collaborative editors.

View on HN

> Tangentially, a cool thing would be to unite ProseMirror with Automerge. That’d enable some killer collaborative editors.

Prosemirror already has collaboration baked into it and I have a very rough initial version of it working (see https://github.com/bangle-io/bangle.dev/tree/master/collab). My question for you is what benefit will using Automerge provide over the inbuilt collaboration API?

Automerge seems more state-of-the-art as far as automatic data syncing and merging goes.

How does it compare to https://github.com/remirror/remirror?

I have been following remirror since the start and also started working on bangle.dev at the same time.

bangle.dev aims to add little API overhead on top of Prosemirror (PM) whereas Remirror tries really hard to hide the PM API and attempts to provide its own React-ish abstraction. This might be a totally fine choice, but I went with the route of building reusable components instead of abstractions.

I'm glad to hear this! Using Remirror worries me because it injects an abstraction between our code and PM.

However, when I look at your docs, it's not clear it's a different in approach from Remirror. The imports are all from bangle.dev which makes it seem like the same approach.

I would love to see a doc explaining the "API overhead" and how to use PM directly. I want to feel confident I can easily drop back down to PM if Bangle doesn't have a feature I need or implements it in a way that won't work for our use case.

Really excited to see this approach! Shared PM plugins are a great idea!

How easy is integration between the two frameworks?

Ours looks fairly similar in the core concept. Less polished. A bit older. Will have to take a detailed look at remirror later!

Update: I created an abstraction called “feature” that seems to be similar to the extension concept, but different. Through features, editor creator can contribute related schema aspects and plugin views. Schema is always there and is not handled by a separate feature, however.

Reply on news.ycombinator.com