this is a niche tweet, but: conventional UI framework wisdom is that we should strive for incremental hydration, rather than blocking the main thread while you make the entire SSR'd page interactive. but! this seems to leave you with a choice:
Either you run the risk of inconsistent UI:
```
<button onClick={increment}>+1</button>
<!-- gets hydrated later... -->
<p>clicks: {count}</p>
```
In this case, the user could click on the newly interactive button without anything appearing to happen.
```
<button onClick={increment}>+1</button>
<!-- gets hydrated later... -->
<p>clicks: {count}</p>
```
In this case, the user could click on the newly interactive button without anything appearing to happen.
Or: you hydrate incrementally, but wait until the end to 'activate' everything and apply current state, in which case you may have kept the main thread unblocked, but really you just delayed interactivity.
Is there a third option?
Is there a third option?
