a criatura em vez de criar um componente para search genérico criou 3 pq na cabeça do mesmo não existe argumentos opcionais
(o cara usou ia no talo sem saber como pandacss funciona e se pah nem como next funciona)
Confiei no meu colega e ele disse que se virava com pandacss.
A ia usou um monte de função css() em vez de usar os objetos de estilo ou ao menos as classes utilitárias.
Cheio de div em cima de div,acessibilidade 0
We have a Chrome devtools extension as a beta release.
While it’s great for debugging StyleX it’s also great for atomic styles in general like with Tailwind or PandaCSS
chromewebstore.google.com/de…
Tailwind CSS is dead.
Look at PandaCSS alternative to tailwind which is being used at Big tech companies.
->Type safety out of the box
->Multi-variant support
-> Zero runtime bundle bloat
panda-css.com/
We also went deep into the journey of building Park UI, why it was built, the problems it’s trying to solve, and what maintaining an open-source design system in public feels like.
#parkui#arkui#pandacss#designsystems
mdr imagine
Une lib css-in-js (pandacss) qui génère des classes css (tw like) qui vont à leur tour être compilées en css-in-js (StyleSheet)
Si un jour je fais ça tuez moi
Je pardonnerais jamais à expo d’avoir démocratiser tailwind on s’est trompé on a créé une nouvelle branche, un univers parallèle. Dans le bon univers où les choses ont du sens tailwind a évolué en un truc typé majestueusement propre et lisible qui s’appelle pandacss 😭😭.
there are just better tools for the job nowadays.
pandacss is easier to learn and use if you want a framework to manage your styles.
chakra is better if you want to rapid prototype or not manage as many components.
vanilla is better if you want full control.