[ericax]

Obsidian developers here! (https://obsidian.md/)

The new editor in Obsidian was made possible by CodeMirror 6, and it has been powering both the Live Preview mode (like Typora) and the source mode in Obsidian ever since.

It can be a bit overwhelming to get into first, but as we experimented more with it, we found it to be extremely extensible and powerful. It's also highly performant for large documents. Another major reason we chose CM 6 is that it's also one of the only code editors that work decently on mobile.

While developing the new editor, Marijn was also amazingly responsive in investigating and fixing all the big and little things we ran into, even relatively niche issues like IME input bugs.

If you find CM 6 useful, consider what you can to support the project! Funding link is here: https://marijnhaverbeke.nl/fund/

[mmgutz]

Why wasn't ProseMirror a fit for Obsidian? Seems like that would be better for structured documents.

[scambier]

For a good portion of its users, an important feature of Obsidian is the use of flat Markdown files.

[mmgutz]

I'm inquiring about actual implementation not Markdown. Markdown -> AST -> CodeMirror vs Markdown -> AST -> ProseMirror.

[ilrwbwrkhv]

What does obsidian use for the graph view plugin? Is it cytoscape? It is very smooth and easy to use.

[ericax]

We use PixiJS!

We used to use d3-force for force simulation, but then we rewrote it in wasm ourselves for performance.

[ilrwbwrkhv]

Huh Pixi JS. I used to be a contributor many moons back. It's a great little library. Would love to read about challenges with d3 force and your wasm approach if obsidian has a tech blog.