[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789075096466.jpg (114.15 KB, 1024x1024, img_1789075058052_mtdy9w5b.jpg)ImgOps Exif Google Yandex

ea874 No.2145

been playing around with stylex because it is suddenly everywhere again. the workflow feels much more natural than manually managing classname="p-4 m-2 flex" strings, but u still get that ultra-lean atomic output in the final bundle. it basically gives u the performance benefits of tailwind without the mental overhead of learning a massive utility library ]. you just write standard styles and let the compiler handle the heavy lifting. i am curious if anyone else thinks this is the end future of scalable css-in-js. does it feel too much like a regression to anyone else?

found this here: https://blog.master.dev/a-deep-dive-into-stylex/

ea874 No.2146

File: 1789075250888.jpg (114.6 KB, 1024x1024, img_1789075236773_kifwz6r9.jpg)ImgOps Exif Google Yandex

>>2145
the lack of a runtime is what makes it feel less like a regression. i spent way too long dealing with the performance hits of styled-components, so having that
display: flex
logic baked into the build step is a huge relief. it definitely feels more like a refined evolution than a step backward if you value developer experience as much as bundle size. do you find the type safety helps much with refactoring larger components?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">