lexical VS js-framework-benchmark

I remember using https://github.com/facebook/lexical for a project a year ago and mostly things worked our of the box.

Any reason to prefer quill?

Lexical (https://lexical.dev/) is really nice to use and doesn't use Prosemirror or CKEditor.

I've tried to get to grips with Lexical but found the docs pretty hard to follow. It definitely seems to offer pretty heaps of power, just unlocking that seemed tricky. We're hoping to use it for customer facing collaborative list product that allows for richer media (video, code blocks etc.)

Yes, it uses the Lexical framework internally, so markdown gets converted to an AST, then the AST gets serialized back.

Rich text editing doesn't imply pagination. Contenteditable is not abandoned. Lexical[1], Meta's framework for text editing relies on contenteditables.

[1]: https://lexical.dev/

lexical is a framework for building web based text-editors ... so yea it can do formatting but if you are using it to just do formatting you are very much using the wrong tool.

Haven't tried it out myself, but it's probably Lexical.

Svelte just got a lot more interesting! Dominic who is the creator of LexicalJs and InfernoJs (which is known to be insanely fast) has joined the svelte core team and is now working at Vercel full time! Here is the announcement on Twitter!

JavaScript benchmarks are instruments for measuring the speed and effectiveness with which a JavaScript engine—such as the ones found in web browsers—can complete particular tasks. Benchmarks are used by developers and browser vendors to evaluate various engines, find places in the code where improvements are needed, and make sure JavaScript standards are being followed.

Strange then that frameworks advertise how fast they are at rendering, mutating, and creating objects in the DOM, and one of the main JS benchmarks everyone likes to measure their performance by is literally a benchmark about DOM manipulation: https://github.com/krausest/js-framework-benchmark

Oh wait. It's not strange. Because state manipulation is a largely solved problem, and even the least performant state manipulation is blazingly fast. However, presenting components in the browser's DOM is tens of magnitudes of orders less performant than anything you can throw at state manipulation.

And every single framework is busy solving one single problem: how do we touch the DOM as little as possible?

It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"

The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark