Olivier Tassinari

We are literally trying to find a solution to this on the Material UI button loading state right now. A proper fix would be amazing.

Switch.Root.Props

[discussion] Create deprecated props to ease Radix Primitives migration? · Issue #601 · mui/base-ui Summary This is an idea that started from: #39 (comment). Maybe it would make sense to create deprecated props for all the APIs that are different from Radix Primitives, making the migration super ...

We could do more to ease the switch, e.g. github.com/mui/base-ui/..., but unclear if it's needed.

The APIs were design by starting from the Radix Primitives API, and then evolving them based on:

- Learnings from Radix Primitives
- Learnings from Material UI test suite
- React 19 new API, e.g. now the ref is a regular prop

Everyone is asking about the differences between Radix and Base UI, which is an upcoming headless UI library we’ve been working on.

@base-ui.bsky.social is here

Watch out for news. I’ve been working on the Base UI docs for the past few months, and this is going to be the component library you didn’t know you needed.

Yay. @base-ui.com just went live 🎉

It looks super promising. I've been eagerly anticipating this because, on paper, it has the potential to combine the best of the Radix API with the ambitions of MUI components and their use cases.

It's too easy to forget that end-users have slow hardware too.

I have reality appreciated working with slow hardware in the past. Any performance regressions becomes so obvious.

Sometimes the best engineering happens when you’re just tinkering, free from expectations and deadlines.