3 ms·
Bingo! For the "requirement of being able to put any element as the radio button.", Dan Abramov tells you that this is exactly the point of React, see his comm
by sam_lowry_ 9mo ago
Bingo!
For the "requirement of being able to put any element as the radio button.", Dan Abramov tells you that this is exactly the point of React, see his comment above:
> For what it’s worth, the point of React is that you can just fix that Radio component to be an input (if that makes sense) and it’ll just be an input. [0]
[0] https://news.ycombinator.com/item?id=46690762 https://news.ycombinator.com/item?id=46690762
- stephenr 9mo agoQuite an ironic use of the word "fix" there.
- chrismorgan 9mo agoYou’re misunderstanding. This isn’t about React, it’s the Radix UI primitives library which is being overcomplicated by it allowing you to put any element as the visual part of the radio button. As for “the point of React” being that you can just do such and such… there’s nothing special about React there, that’s what any of these component libraries achieve (React, Vue, Svelte, &c., even basic templating systems like Handlebars a lot of the time).
- sam_lowry_ 9mo agoAm I? I was just quoting the React creator.
- chrismorgan 9mo agoRadix UI Primitives has placed this requirement on itself. What you’re quoting amounts to “component abstractions allow you to easily throw Radix UI Primitives away” which is irrelevant.