acywatson

@trueadm Why didn’t they send the robots on the spaceship instead of the actual people? Also how does that chip reader not have a PIN or some other second factor for auth? That episode stressed me out.

I missed Black Mirror.

@ProofOfKeags @lexicaljs I'm not sure I fully understand which functional aspects of Draft you're referring to. Is it the idea that you get a new EditorState back from the imperative APIs in Draft? How do you think Lexical patterns clash with React hook patterns?

@lexicaljs Why did the team opt for a highly imperative approach as opposed to the functional approach taken by the predecessor DraftJS? I'm finding it significantly harder to use and wrap my head around, especially since it clashes with the react hook patterns.

@trueadm Congrats man!! Stoked to see what you build :)

I’m excited to share that I will be joining Vercel next week. I’ll be joining the awesome folks on the Svelte core team! 🔥

@moreofmorris @lexicaljs @nextjs @reactjs For sure - we have heard this feedback before, so you're definitely not alone in feeling this way. Trying to figure out the best way to address it is an ongoing process, though :). Thanks to feedback like this, we're starting to get some good ideas.

@acywatson @lexicaljs @nextjs @reactjs Not to say it’s all bad, though! Once the whole thing starts clicking, it’s good stuff. It’s just that the initial ramp up is so steep, which is a shame as Lexical is so powerful and flexible. But I can see easily see how the docs would scare people away.

I’ve been on a mind-bending trip to hell and back with @lexicaljs over the last few days… but it’s starting to make sense now. Where the @nextjs docs and the new @reactjs docs are excellent, Lexical still has a long way to go for theirs.

@moreofmorris @lexicaljs @nextjs @reactjs Makes sense - really appreciate your thoughts :)

@acywatson @lexicaljs @nextjs @reactjs Hey! There are many concepts to understand, which feels overwhelming, but the docs don’t provide order, depth, or specific examples. Putting it all together is hard. The playground is good, but also overwhelming, so maybe more targeted, real-world examples would help there, too.

@brian_d_vaughn @lexicaljs

@trueadm The team’s gonna miss you, but we’ll all be eagerly waiting to see what amazing thing you come up with next! 🫡

Today, I am sharing the news that after 6 years, I will be leaving Meta early next year. It’s been an awesome journey and I’ve had the privilege of being able to work on so many great projects, and learn from so many talented people.

@skies_dev @lexicaljs This is cool! Glad you took the time to try it out. Lots of golden nuggets of feedback in here for us to use to improve the docs and DX :)

i made my first youtube video let's try @lexicaljs, the rich text editor for react 😀 youtube.com/watch?v=1I6jLB…

@jackhanford @lexicaljs @LatticeHQ Love it - thanks for sharing!

We've recently fully rolled out our new @lexicaljs based Rich text editor at @LatticeHQ (~65 instances, many unique designs) and have seen a 99% decrease in RTE related errors, exceptions and tickets 🔥

@DanielFGray @lexicaljs Definitely a priority - made some minor progress over the weekend: github.com/facebook/lexic…

@lexicaljs Documentation would be good 👍

We're looking at how we can best engage with the Lexical community. Are there any podcasts, streams, or other idea folks have that they'd like the core team to be involved in? We'd love to discuss ideas and share thoughts on the future of the project.

@EricVicenti @reactnative @lexicaljs @amyruthworrall do we know anyone on the React Native Team? :)

@reactnative hey @lexicaljs, do you know anybody on the React Native team?

Maybe I'm asking for too much, when I ask for a rich text editor in @ReactNative I'd settle for a working-class text input component

@shreyacasmalert @reactjs @lexicaljs - still lots of interesting work to do here!

Hey tech twitter, I'm looking for open source projects to contribute, mostly in the frontend space. My tech stack is @reactjs. Share your recommendations below 👇

This is awesome to hear!

@amyruthworrall @lexicaljs what about “x”? xGetRoot() xGetSelection() No semantics there, just a random idea :)

The @lexicaljs API convention is to start function names with a $ if they need to be run inside an update block. Anyone any ideas of what we could do in Swift (which doesn’t permit starting functions with $)?