And if you look at the horizon, you might spot our next big release 🚀

The pull request can be found here: github.com/DigitecGalax...

Performance can be improved, but we're waiting for feedback and issues before we tackle that.

And it's noticeable from the outside. Very good job in setting up such a prosperous environment

We got so many issues in our production page that this update seems less than half baked. Even apples own pages have issues

But you could use conditional exports to hide this complexity from the user. ${theme =>...} Would read from the context in "classical" react environments and from `cache` in the RSC environment.

💯

Totally agree.

All of those options are viable, but had downsides for us, as we rely heavily on styled-components and didn't want to migrate away from the flexibility it gives us. `pigment-css` tried the same but with the core of linaria the build time becomes a major concern.

We developed `next-yak` (yak.js.org) exactly for this reason and use it on a huge application. What are your thoughts on static extraction?

We have a way with `next-yak` to address exactly this part. It looks the same from a user perspective, but we do different things depending on the current render context

Yeah I think the docs aren't wrong or advocate it wrongly, but I get the feel that the hook is the main implementation and startTransition is the thing that you can use if you can't use hooks. Maybe it's the amount of examples and documentation yes

I get the caveat now, but the text indicates you should use it where you can't use `useTransition`

react.dev/reference/re...

Would that mean that we always should use startTransition and only use useTransition if we specifically need the sync isPending state? The docs indicates it the other way around 🤔

Interesting thoughts.

How would you handle code that most of the times updates together but there are only certain components interested in the state of it (e.g. a user and we want to show the profile picture in the header and the user name somewhere else and his friends also somewhere else)?

What do you think about external state management solutions that don't suffer from this issue (e.g. jotai)?

Ideally yes. We were thinking of some form of deduplication. But this is easier said then done, because we don't want to have the same constraints as e.g. stylex has, to not be able to use selectors that target specific children, nor do we want to run into ordering issues.