Both of those are coupled to React/JSX unless I'm mistaken.
The reason we've chosen DaisyUI (which seems similar to Hyper) is that its framework independent and just uses CSS (no JS) as our team uses Svelte/SvelteKit.
In my experience this gives you more flexibility while still giving you a lot of the common UI boilerplate you need to scaffold apps quickly.
Being able to use a single component library across UI frameworks is a huge advantage.
If you're implementing a reasonably complex ui, the insane edge-cases that component-libraries must manage cannot be accomplished with CSS alone. Accessibility, Keyboard-Navigation, spec-conformance... The feature summaries from react-aria [1] illustrate this.
For example, did you know that it's not trivial to have a button inside an interactive list item, because none of the default html-interactive components can be nested?
As another example, DaisyUI recommends relying on the <dialog> element for a simple modal, which, as I recall, has flawed accessibility and excludes 7% of browsers.
Radix has some great ideas that challenge the way components are usually built. I'd love to use it, but am somewhat burned by how Stitches stopped being maintained due to the changes in React 18. Context: https://github.com/stitchesjs/stitches/discussions/1149#disc...
To be clear, it's not so much that they decided to not spend time, energy and money into maintaining it, but that there's seemingly been very little (if any) interest in letting others maintain it despite several people expressing interest. I'm sure it's scare handing over commit access, but if you're giving it up anyway then why not just do it, see what happens? Instead it's just dead in the water.
I'd happily pay license fees to use Radix and/or Stitches, if that guarantees maintenance. Sadly that's not an option it seems.
is Radix so tied with Stitches? that would be a bummer. I'd rather not tie myself to (another) CSS-in-js solution, both because RSC are looming and because I don't want to pay a runtime cost to apply CSS classes
It's maintained by the same people, and the problem isn't so much whether there's a hard dependency on Stitches, but the way they've essentiellt swept the rug under the feet from anyone using Stitches leaves a bad taste in my mouth and makes me hesitant to use Radix.
Glancing through the examples, Radix reminds me a lot of MUI.
This is not a bad thing, I’m just not sure how “nothing comes close” to Radix. Radix doesn’t seem obviously better? (Maybe it is, I have no experience with it.)
it doesn't have multiselect neither does shadcn which is based on it. Basic command is buggy, if you delete a character while searching it would stop showing the options. Documentation also assumes that you already know radix and other libraries not as clear as other sites. Yet somehow it has captured the attention of everyone.
I am the author of the library and I have really put huge effort on the Combobox component and the documentation. Please take a look if you want and let me know what you think!
