[hitekker]

Nice overview on the pros of ProseMirror.

When you were surveying the editor-landscape, what made you choose ProseMirror over its competitors?

[mattberkowitz]

At the time we started revamping our editing interface many of the options were still in early/incomplete places. I think ProseMirror had an funding campaign at the time that didn't meet its goal initially, although did later on in a second attempt. Ultimately we decided to venture down the path of building our own editor, which was based on a combination of our own learnings in text editing and a collaborative system some folks in our graphics department had put together.

About 6 months in, near the start of 2016, when moving on from the exploration/demo stage of the project to actually building out the real deal we took another look at the landscape and decided to move to ProseMirror. I don't remember the exact points that went into the decision but transitioning from our in house solution to ProseMirror felt pretty natural as they followed similar design philosophies.

[hitekker]

Thanks for the response!

You went down the hard path of rolling out your own editor, and used the knowledge gained to choose a worthy successor.

I'm impressed. I should give ProseMirror another shot.

[mattberkowitz]

I also think the fact that Marijn had CodeMirror on his resume helped with our willingness to take a risk on a pre 1.0 library

[leeoniya]

i think the most similar lib to ProseMirror is http://bustle.github.io/mobiledoc-kit/demo/

[Sir_Cmpwn]

I think they just told you?

[hitekker]

There is some overlap between the points listed and the features other editors offer. Unidirectional data model for example is also in SlateJS.

More pertinently, I’m interested in what made them choose ProseMirror at the time, as opposed to what they like about it now.