3 ms·
I was honestly curious until I hit the listbox comparison. The implementations for competitors look purposefully verbose to make Nue look better. The Svelte one
by ttfkam 3y ago
I was honestly curious until I hit the listbox comparison. The implementations for competitors look purposefully verbose to make Nue look better. The Svelte one in particular could look substantially similar to Nue, but after adding multiple seemingly useless layers and type definitions on top to get the same effect.
Once I saw that in the Svelte example, I couldn't help but wonder if the same applied to the others as well. It all seemed to me beyond simple marketing puffery and into uncharitable and misleading territory.
And honestly:
<select name="Cars" size="6" multiple="multiple">
<option>Mercedes
<option>BMW
<option>Jaguar
<option>Lamborghini
<option>Ferrari
<option>Ford
</select>
Sometimes you need a custom skin all decked out to the nines, but real talk, most folks just need to use the plain old HTML, apply minimal CSS, and move on to the next task.
- ttfkam 3y agoI'm realizing that someone is going to hop in and say, "But that's limited to just a line of text per option with no images or real formatting." And that's true. It's also true that's what most folks actually need in most cases. That said, another fast implementation using more markup is to have either a hidden radio button group (single selection) or bunch of hidden checkboxes (multiple selection) that are referenced by visible label tags for the rendered listbox. Doesn't break accessibility for screen readers and can even work without JS. Browsers can do so much out of the box without us constantly reinventing the listbox wheel.
- dannyfritz07 3y agoThe "React ListBox" is actually the code for Tailwind's headlessui. I honestly think the bloat in the React ListBox impl is an example to not use Tailwind's headlessui component and less an argument for why to use Nue.
- deleted 3y ago[deleted]