3 ms·
e.g. using mui sx. the downside is the runtime performance cost https://mui.com/system/getting-started/usage/#performance-tradeoffs https://mui.com/system/gett
by willsmith72 3y ago
e.g. using mui sx. the downside is the runtime performance cost
https://mui.com/system/getting-started/usage/#performance-tradeoffs https://mui.com/system/getting-started/usage/#performance-tr...
i don't want to reuse or compose my styles, i just want to add alignSelf: 'flex-end' and then easily be able to change it and see the styles in one place, without leaving the component definition. the reusability and composition is at the component level
- cantSpellSober 3y agoThanks! Great reason this beats MUI. Not trying to hate on atomic CSS, composable classes and style tokens are good. Even one of the devs on this project commented on them here: > We don't think the Tailwind way of styling is readable in the long term, but we see the value is being able to author that way https://news.ycombinator.com/item?id=38540629 https://news.ycombinator.com/item?id=38540629 The docs here mention the downsides though.
- willsmith72 3y ago> Great reason this beats MUI. Not at all, mui gives you the option to do either. I don't want my style library being opinionated about my coding style.
- cantSpellSober 3y agoOhh I see, I honestly didn't click the first time. You meant sx in MUI, not StyleX. We're gonna need more names.