Rethinking Rich Text: A Deep Dive Into the Design of Lexical - Acy Watson

[@AbdelhameedG]

That was so enlighting thank you , for sorry the talk ended before you finish :(

[@ivailop]

Thank you for this talk! Very insightful!

[@prat_0501]

Thank you so much for this talk! ❤

[@benthomson2406]

great video to explain a lot of core concepts about the rich text editor🥳

[@haritssyah7434]

Can I get the slide from the presentation? Looks like the presentation is not finished, and I am curious about the rest of the slide which is not presented. Thank You.

[@AbhishekKumar-hr1sr]

How can I get access to these slides?

[@kylealwyn3127]

Really good stuff

[@zummotv1013]

should I use lexical for a serious project?

[@nsrc9583]

Depends on what you mean by serious. I've worked with Lexical, and it's extremely extensible. But, because of how bare-bones it is out of the box, you will have to assemble a lot of things yourself. Really, it's an API for the kind of virtual DOM you'd need to make a web-based text editor. Depending on how complex you want your editor to be, making a frontend for that DOM can take a long time because of how slim their documentation is (Lexical is still very young). But, I think it's the best editor if you really want a custom text editor.

[@DeluXeZ3niiTh]

@@nsrc9583 Even more barebone than something like ProseMirror ? How does it compare ?

[@刘鲲鹏-t7w]

I found that it seems to take almost exactly the same framework as ckeditor5,so who reference whom?

[@naranyala_dev]

the new "react"