Moving from remarkable to markdown-it ?

Just a thought, since (see here):

markdown-it is the result of the decision of the authors who contributed to 99% of the Remarkable code to move to a project with the same authorship but new leadership (Vitaly and Alex). It's not a fork.

It seems like markdown-it is better option. API should be pretty similar, as projects are almost clones.

It's a great suggestion @pawelgalazka, I've been looking into it, the only thing I'm still missing to figure it out are the custom fence blocks.

It would be nice if we could figure out a way to allow the parser to be passed so that people could use their preferred parser. There are so many out there, e.g. remark remarkable markdown-it marked (no longer maintained but used everywhere) etc., and everyone has their own preference. I understand that this may be very tough if certain parser options are used for the actual react component insertions. Feel free to disregard but I do think it would be something cool to think about.