Thread by @acdlite

I've been trying to write about Concurrent React, but I'm finding it difficult because everything is so interconnected.

So I'm starting from scratch with a new approach: write all the topics down, flesh out the details, then break and edit the result into managable pieces.

These are really rough outlines, mostly notes for myself so I don't forget later.

I'm finding it hard to query my brain for all the interesting things. If there's something you'd like to know about Concurrent React or Suspense (or React in general), let me know!

And then maybe that will motivate me to stop yak shaving and write the damn docs already. Get it together, Drewfus!

I threw out my previous attempts to document this stuff because I struggled to find the right level of detail. I really DO NOT think that most React devs will need to know about most of this stuff. But it should still be accessible, somewhere. Maybe a separate section of the docs

And it's hard to give you just a piece of the puzzle, because without the full picture it might lead to the wrong inference. Concurrent React is not quite like the event-based, push-based model most people are familiar with. It's intuitive once you "get it" — not immediately.

I wish I could distill it down to "five things you need to know" but if such a formulation exists I have yet to find it (though we keep getting closer).

IOW we have a pretty clear mental model our heads but it's not one that I've figured out how to succinctly communicate.