async

[tombl]

this shouldn't be a concern of the core library, but I definitely want to work out some patterns/utilities for handling async data and code.

I don't want to end up with something like suspense, because that feels too much like the library is driving the data rather than the other way around, but it provides probably the best UX and DX of anything I know of.

whatever we end up with, I would like for most of the app to be async-blind, and not to have spinner hell.

I wanted to avoid thinking about this all together, and just use local-first type synchronous data, but then I remembered code splitting exists and is important.

[tombl]

an obvious thought: maybe async (code) handling is purely a router concern? besides for route splitting, how often are people calling React.lazy?

in other words: assuming suspense is just for code loading and not data fetching (like the good old days?), how many people just have a single toplevel boundary?