I love this aesthetic and vibe! 10/10

Good thing then that I'm giving a talk in 4 days at Rust Forge on (among other things) making inference breakage no longer actually break things 😁

And my favorite new feature, fade out branch tree on hover.

The search was significantly improved.

I would be asking myself, but why? all the time.

The whole `const isStale = query !== deferredQuery` pattern only works because the sub-tree renderer doesn't want to update the deferred value, while a suspension is going on.

This made it extremely hard for me to wrap my head around even the simplest examples in the React docs.

But at the same time I feel like some of the design decisions are accidental. <Suspense>, the fallback argument and `use` feel like a whole thing! Very clear how they work and interact with each other.

On the other hand, `useDeferredValue` feels like a hack that is not really part of the system.

This interactions allow for very creative UI patterns.

For example, detach search from the input field and fade stale results while waiting on new ones with just a few lines of code: react.dev/reference/re...

Even if a <Suspense> block catches the `use` "exception" before, `useDeferredValue` is still aware of it. They are two different systems.