Is base-ui a reliable choice for enterprise frontend libraries? #3578
Description
I want to design a frontend library where I integrate @mui/joy styles on top of base-ui, but we’ve had problematic experiences with mui in the past. Initially, I built a library based on @mui/material 5.x.x, and when moving to 7.x.x I realized that too many things had changed. I was going to start using @mui/base, but then I encountered a declaration stating that everything would eventually be managed through base-ui.
After that, I moved away from Material and built a library on top of @mui/joy, but midway through development I received information that support for that library was being discontinued. I really like mui’s support speed and ecosystem, but I’ve also been disappointed at certain points.
I’m designing a library for a large insurance project—so do you think base-ui is a safe choice?
Why should I choose base-ui instead of shadcn, chakra, or mantine?
What is the differentiating advantage of this library? I genuinely want to understand this.
Will we receive long-term support for this library, or will it fade into uncertainty like MUI/Joy? :)
I’m sure this is a question many people have in mind.