milkdown VS yjs

Page: https://milkdown.dev/

When it comes to community plugins, I don’t run a single one. The core plugins do what I need. I only miss two features, scrollable code blocks and support for WYSIWYG tables like in the Milkdown editor. To my knowledge, there are no community plugins for this, so I haven’t had any reasons to install such plugins. I guess I’m a quite basic Obsidian user.

To be honest, there are not many disadvantages. There are some annoyances. I personally miss a good way to build tables. A table-building solution like the one in Milkdown (visual Markdown editor used by e.g., Standard Notes) would be very welcome. I also miss horizontal scrolling in code-blocks and other such minor stuff. Since Obsidian is improving in a high pace, and hasn’t even reached version 1.0 yet, I can live with that.

When writing a list in the new Markdown Visual (which seems promising despite the misfortunate font choice), I am not able to indent a list item using tab, like you do in all other writing software. As I understand it, it is based on the Milkdown editor, which states in their shortcuts that it is Mod-[ or Mod-] to sink or lift items.

Sounds like you need a WYSIWYG editor. There are a bunch of them, but I like Prosemirror and Milkdown the most.

Milkdown is a WYSIWYG (what you see is what you get) editor. It's an open source project that integrates Markdown editor, components, and plugins.

HyperMD and Quill are pretty nice. The one I currently have my eye on is one called Milkdown (https://milkdown.dev)

Hi guys. Just made an editor wrapping around Milkdown, the WYSIWYG Markdown editor component. Here is the installation link:

One idea is just to use fewer random bits in peerIDs. Yjs (https://docs.yjs.dev/) gets away with just 32 random bits. If you compromise and use 64 random bits, then even a very popular doc with 1 million lifetime peerIDs will have a < 10^-7 lifetime probability of collision.

I've seen it come up often in collaborative text editors.

Also see: https://github.com/yjs/yjs

You are absolutely right that XML is better for document structures.

My current theory is that Yjs [0] is the new JSON+XML. It gives you both JSON and XML types in one nested structure, all with conflict free merging via incremental updates.

Also, you note the issue with XML and overlapping inline markup. Yjs has an answer for that with its text type, you can apply attributes (for styling or anything else) via arbatary ranges. They can overlap.

Obviously I'm being a little hypabolic suggesting it will replace JSON, the beauty of JSON is is simplicity, but for many systems building on Yjs or similar CRDT based serialisation systems is the future.

https://github.com/yjs/yjs/

Note: https://github.com/yjs/yjs for collaborative "document edition, and user cursors"; has WebRTC, web socket, matrix.org backend

CCP needs to revamp proto anyway, due to recent exploits... practically, nothing really prevents 'em from using some sort of CRDT's to make the state of the sig view eventually consistent (yjs lib, if we're speaking frontendian).

Yjs framework: Because it is a CRDT implementation which provides collaborative editing and offline-first capability.

No problem. The database CRUD features are just helpers as an abstraction on top of yjs: https://docs.yjs.dev/. Eweser adds schemas in the form of typescript types to make using it simpler, more structured, and interoperability easier.