Re:Facebook open sources Lexical, an extensible text editor ...
by distrill on Wednesday April 13, 2022 @08:43PM
(#31022122)
GP may be responding to the fact that the vanilla quick start page is empty while the react one is not
Re:Facebook open sources Lexical, an extensible text editor ...
by trueadm on Wednesday April 13, 2022 @08:45PM
(#31022133)
Yeah, we're still working on our docs. Watch this space! :)
Re:Facebook open sources Lexical, an extensible text editor ...
by kingcharles on Thursday April 14, 2022 @12:45AM
(#31023500)
It would seem the very first thing you would do is provide an example for vanilla JS so that everyone could get started. It is impossible to use this at all for the large proportion of the world that isn't using React as we can't even see a single example.
If it's so complicated to use that it takes more than a minute of vanilla JS coding to initialize it, then I don't think I'm interested, thanks all the same.
Re:Facebook open sources Lexical, an extensible text editor ...
by motoxpro on Thursday April 14, 2022 @03:05AM
(#31024141)
They use it internally, why would they rebuild it in vanilla before they released it? Sounds like they are working on it even though it's of no use to them.
Re:Facebook open sources Lexical, an extensible text editor ...
by endisneigh on Wednesday April 13, 2022 @08:57PM
(#31022217)
yeah - I didn't see any examples on how to use this without react.
Re:Facebook open sources Lexical, an extensible text editor ...
by akemichan on Wednesday April 13, 2022 @09:10PM
(#31022315)
Any particular reason Meta decided to implement it's own editor library instead of building on top of ProseMirror?
Re:Facebook open sources Lexical, an extensible text editor ...
by trueadm on Wednesday April 13, 2022 @09:23PM
(#31022390)
ProseMirror wasn't a good fit for us because it's integration (especially with React 18+) isn't quite there. Furthermore, we're also looking into building native ports of Lexical, and given's Lexical's API isn't DOM centric, it allows us to do that.
Lastly, we found ProseMirror was too heavy in terms of bytes for very minimal almost plain-text interfaces where we only wanted mentions + hashtags + custom emojis. Lexical comes in at around 22kb min+gzip, so it works really well for us.
The reason we have React bindings from the start, is because we needed these internally at Meta.