Sorry, this was a bad attempt at a classic blue/red async function joke. The concept seemed relevant here though. What if we stopped trying to make handling “red” operations/events within “blue” components ergonomic…just make everything red.

"Solid 2: Red Version"

Our design system is actually all Lit web components underneath which helps since those get reused no matter if the remote view/micro-app is built with React or Angular.

We have wrappers like this that interop props and events between frameworks invisible to the dev. We even have a custom wrapper API around Tanstack Store that lets teams export/import remote stores with public and selectively private actions for subscribing and interacting with shared state too.

I know ideally there is a more declarative way to handle that situation somewhere in works standards-wise, but curious if this might enable a slightly better solution until then?

Will this open up a path to optimizing SSR'd web components like with Lit SSR? Specifically, the stye duplication bit that has to happen for that to work nicely today.

"Customize & Reorder" tip I saw somewhere. At least feels a tad closer to the old setup:

Oh, both approaches certainly each have their pros and cons. I’ve just always thought the differing sentiment was funny.

Felt some type of way when this happened:

@cache() - 🤢
‘use cache’ - 😍