RF21 - Naman Goel - Rethinking CSS - Introducing Stylex

[@rand0mtv660]

Yes finally! I've been waiting for some info about Stylex ever since I've read in some twitter thread that it's going to be open sourced a long time ago.

[@NeerajLagwankar]

Can't wait for this to be open sourced

[@bscodev]

Interesting. I look forward to the open source from Stylex.

[@최원영-p3t]

when can we use stylex? i can't wait 🥴

[@weebatheart]

Please open source this!

[@AndrewBone]

styled-components still feel more flexible to me. Though I'll look into it more when it's fully released.

[@dealloc]

Styled Components inherently have some issues which affects both UX and DX; client-side runtime (requires double render to compute in SSR and CSR, can be poor for UX), duplicate entire component's CSS for when using dynamic values (worse if you have multiple permutations of often-changing props you pass to a styled component), no proper API for making variants (either use data-attributes, CSS variables or create components for each variant-again dynamic props lead to duplication), even worse compound variants are difficult to do. If you haven't already I can recommend looking into Stitches and vanilla-extract/sprinkles which provides styled-like API but much less overhead and comes with APIs for theming, variants and compound variants.

[@stereocodes]

I really don't like the react native API imposed on my CSS. Please tell me I can use regular style properties and that the react native flavor is optional.

[@SandeepMishra95]

Yeah this is optional and not tied to react in any way. It’s just a CSS-in-JS solution which generates static CSS in build time.

[@designbykhalid]

Reminds me Tailwind CSS