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.
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.
[1]: https://react-spectrum.adobe.com/react-aria/useGridList.html
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.
HyperUI is useful for server-side sites too e.g. Rails, Laravel etc
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.)
I work in a design agency and I’ve always struggled with component libraries because they weren’t flexible enough.
Radix has been a godsend and such a pleasure to use.
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!