Replies: 2 comments 1 reply
-
The As you can see it is a lot closer but still a bit lower. I think it's because other libraries offer higher level APIs than we have historically offered, which developers find attractive. That's one of the reasons we're working on react-aria-components. |
Beta Was this translation helpful? Give feedback.
-
+1. If not for react-aria (and framer), I would exit react for truly reactive framework like qwik for solid. Have tried most of the other UI frameworks, which are like candy to a baby for how easy to get up and running, but always end up hitting a wall at some point where I spend more time working around the framework or overcoming limitations than the time saved. React-aria is first framework where gets out of my way, but has a steeper learning curve. Great UI framework as makes me feel like possibilities are endless. Thank you!! |
Beta Was this translation helpful? Give feedback.
-
Why isn't react-aria as popular as other libraries/frameworks? I came across this link, https://npmtrends.com/@ariakit/react-vs-@headlessui/react-vs-@radix-ui/primitive-vs-react-aria-vs-react-aria-components, and it seems like react-aria is not getting much love as a low-level headless component library. I've also noticed that Radix is getting a lot more attention on Twitter. But I don't get it. To me, react-aria is a super complete, complex, battle-tested library from Adobe. Can someone explain why this is happening? Or maybe npmtrends isn't the best way to measure popularity?
Beta Was this translation helpful? Give feedback.
All reactions