@colmtuite@pacovitiello I'm building something fun with Base UI components but torn between shadcn and coss ui. Is the consensus that coss ui is more polished and stable? I prefer the design too, those dialog footers are solid.
@adamwathan@malfaitrobin do you have a timeline for non-Vite bundlers to rely on the module graph rather than crawling entire project? Specifically Next.js
I understand itโs a very complex task. Are there any critical blockers preventing you at this time? Thanks!
@jeffrey_way A mix of all. Itโs not yet ready to replace senior+ engineers. The quality is questionable. At some point, AI will face stricter limitations, either due to operating costs or memory issues. However, future engineers will be forced to use AI as a daily assistant.
@panda__css Thatโs the plan at Zillow! Weโre taking it one component at a time, starting with our design system. I respect styled-components and its history, but performance and business needs have led us to Panda CSS ๐ผ
@olivtassinari The shift from `asChild` to `render` prop for polymorphic components is pretty interesting. `asChild` made it easier to work with `forwardRef`, but now that React 19 treats `ref` as a regular prop, using `as` or `render` props is way simpler to type in TS.
@panda__css@thesegunadebayo@_estheradebayo
My manager has bought the Panda Mastery team license, but we don't know how many seats per license there are and how to activate individual seats. Would you mind helping out? Thanks!
@brijeshb42@olivtassinari@JoshWComeau Sure, here is a sample ButtonGroup component that needs to support 3 responsive props with 2 of them being compound props. Of course it does not work, but you can get the sense of the API use case, etc. This is heavily influenced by Panda at the moment. https://t.co/7ydWTUuRNp
@kaumac@JoshWComeau@olivtassinari Got it. Iโm staying away from the styled factory. Itโs the Bain of my existence at work with styled-components. Decided to go with Panda and use className exclusively. Much cleaner implementation.
@tlakomy I've been there and done that for 19 years. I'm not going back until ***, Januszex, and the ever-present ads are gone ๐ That being said, I still have a soft spot for all the old Polish comedies๐งธ
@kaumac@JoshWComeau@olivtassinari What specifically do you have to fight and what limitations? Would love to know as Iโm embarking on a long journey with Panda.
@JoshWComeau@__smiz A component with props and variants would still require some runtime code on the server and client to match prop values to variants. Either custom implementation or a built-in library utility. Unless youโre able to completely strip unused variants and mapping at build time.
@__smiz@JoshWComeau That being said, the future of CSS-in-JS is the static CSS extraction with minimal prop value to variants mapping, and variant pre-generation. Thats the most performant solution w/out going full vanilla CSS or CSS Modules.
@__smiz@JoshWComeau Not on a single component, but when you have to render 100, 500, 1,000 components, it adds up. styled-components affects Total Blocking Time, which negatively affects Interaction to Next Paint. Add a few slow event handlers and Core Web Vitals are gone.
@__smiz@JoshWComeau Lastly, siloed performance benchmarks are mostly pointless. No website loads a single instance of a component and multiple component instances do not translate into linear performance deviation. Add React 18 and concurrent rendering to the mix and things will get even trickier.
@__smiz@JoshWComeau On the other hand matching prop values to variants depends on implementation. For example, CVA (class variance authority) vs clsx vs Tailwind Variants vs built-in utilities like cva/sva in Panda CSS.