[jsf01]

Just at a cursory glance, this looks pretty verbose and clunky. Existing React ecosystem styling solutions are many, so it’s not immediately evident to me when you would accept the trade offs introduced by this tool over any existing ones that seem much nicer to not only integrate, but also have to work with day to day.

[willsmith72]

0 runtime is the argument over emotion (and therefore MUI right now)

[scoot]

You'll be glad to hear that MUI is zeroing in (pun intended) on a zero runtime solution right now as an alternative to Emotion [0], although that GitHub issue doesn't capture just how far it has come. Expect more soon!

[0] https://github.com/mui/material-ui/issues/38137

[nsonha]

they are not the same kind of thing though, one is a library TO WORK WITH styles, the other is a library AND some styles

[muratsu]

thanks for pointing this out. I hope they extend their `thinking in stylex` page with this info.

[cantSpellSober]

They do, albeit it's a bit confusing

https://stylexjs.com/docs/learn/thinking-in-stylex/

> There is no runtime overhead here

Specifically

> No runtime style injection.

There's still a runtime though

> Optimized runtime for merging class names.

[chalsprhebaodu]

They explain the 0-runtime pretty thoroughly.

[swyx]

it was exciting at launch, but took forever to ship, and now Tailwind has run away with that problem.

[ryanar]

Announced at React Conf 2018, I was so hyped for it back then! I did not expect it to take 5 years.

https://youtu.be/9JZHodNR184?t=270

[agos]

We should keep this in mind and adapt our expectations about forget, the compiler that they announced like one year ago

[swyx]

already forgotten

[xixixao]

Agreed! It’s been used internally at Meta for so long, but I don’t miss it after adopting Tailwind.