Starting today, we are making @base_ui the default component library in shadcn/ui.
First, a bit of history. When shadcn/ui launched in 2023, it was built on Radix. At the time, nothing else came close. Headless. Accessible. Composable.
Fast forward a few years and the team who built Radix are building something new: Base UI.
in an effort to save token spend, i’ve started asking llms to assign a reasoning level to each task and prompt me to manually switch models whenever it changes… really wish this was possible in codex w/o HITL. is there some config magic i haven’t learnt yet?
this is the part ppl often don’t consider… if you’re using tailwind-merge, you’ve added a css-in-js runtime layer, and it can be slower/larger than alternatives (e.g. @stylexjs or @tokenami_)
StyleX has similar performance to Tailwind unless you use tailwind-merge which is very slow. StyleX has better guarantees than tailwind-merge built in while being smaller and much faster.
i met a team that reignited a fire in my belly i just couldn’t resist... so, i’m excited to share that today is my first day helping shape @base_ui with the incredible MUI team 🎉
huge thanks to everyone who supported me during my job search, and all the amazing ppl i met along the way!
hmm, i took the opposite approach. i guess it might have something to do with intractability.
e.g. usually when you move something around you need to pick it up, so the shadow underneath the object would grow denser.
also listen to the sfx ; )
tailwind didn’t win bcos adam threw tons of projects at the wall to see what sticks. it won bcos he believed in something few did, and dedicated years to that conviction.
conviction builds products. without it, most quit before they win, and ai can’t help with conviction.