4 ms·
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 an
by danaw 3y ago
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.
- SebastianKra 3y agoIf 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. [1]: https://react-spectrum.adobe.com/react-aria/useGridList.html https://react-spectrum.adobe.com/react-aria/useGridList.html