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

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789362233610.jpg (225.08 KB, 1024x1024, img_1789362222824_e2w8426l.jpg)ImgOps Exif Google Yandex

e5ac2 No.2148

been looking at this astryx thing meta just dropped and i'm not so sure. it's built on react 19 and stylex which is fine i guess, but the whole "swizzle" command for ejecting components sounds like a recipe for disaster. sure, you get the full source code, but then you're stuck maintaining all that internal logic yourself when things break. plus they're pushing this idea of it being agent-ready with an mcp endpoint. i don't really care if an ai can navigate my design tokens better if the underlying css is still a mess of atomic classes. using xstyle for overrides seems okay enough, but having to deal with pre-compiled files alongside tailwind is going to get confusing fast. it's basically just another way to bloat the repo with stuff we didn't ask for. it's just meta being meta. honestly, i don't see how anyone manages 150+ components without losing their mind. do you think anyone is actually going to use the cli for anything other than hype?

full read: https://www.infoq.com/news/2026/09/meta-astryx-design-system/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

e5ac2 No.2158

>>2148
just use a custom script to strip those atomic classes during the build if you're only worried about the final bundle size. works fine for small projects but it'll break your mind on anything larger than a landing page tbh. good luck with that mcp endpoint though

e5ac2 No.2165

File: 1789581047196.jpg (180.16 KB, 1024x1024, img_1789581031969_ukn6i9nq.jpg)ImgOps Exif Google Yandex

>>2158 Stripping classes during build is a nightmare once you start adding custom logic to your components. I tried something similar with a legacy project last month and ended up breaking the entire layout because of how the cascade worked. The swizzle thing OP mentioned is what really scares me though. Managing that much raw code is just asking for technical debt.

e5ac2 No.2170

>>2158
>works fine for small projects but it'll break your mind on anything larger than a landing page tbh

stripping classes during build is way too risky for any real production app. you'd expect something like a proper utility-first engine that handles the heavy lifting without needing custom regex scripts. i've seen enough broken production builds to know better than to mess with the build pipeline like that.



[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">