7 ms·
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
by jsf01 3y ago
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 3y ago0 runtime is the argument over emotion (and therefore MUI right now)
- muratsu 3y agothanks for pointing this out. I hope they extend their `thinking in stylex` page with this info.
- chalsprhebaodu 3y agoThey explain the 0-runtime pretty thoroughly.
- deleted 3y ago[deleted]
- cantSpellSober 3y agoThey do, albeit it's a bit confusing https://stylexjs.com/docs/learn/thinking-in-stylex/ 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.
- scoot 3y agoYou'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 https://github.com/mui/material-ui/issues/38137
- nsonha 3y agothey are not the same kind of thing though, one is a library TO WORK WITH styles, the other is a library AND some styles
- swyx 3y agoit was exciting at launch, but took forever to ship, and now Tailwind has run away with that problem.