I really love the way you talk and explain. To the point, but not too fast. Very clear. The topics are more advanced compared to 90% of dev youtubers, who seem to focus on very beginners almost exclusively. I like that you are not doing this. One of the reasons I didn't want to use react-aria where changes like `onClick` to `onPress`. But your explanation made so much sense. Keep it up dude, you are on the right track!
This is the best react-aria-components video I watched. Your examples for each features are absolutely wonderful. I will give a try your lib. Thank you.
is it though? 5 hours later I'm still struggling to implement a ToastProvider. their typescript examples are weak at best imo. i want to love it, but man is it making it hard.
Excellent work man, thank you for making this! Been building out a design system using the react-aria components with the tailwind-variants library and your codebase is a really great reference for how to do this type of thing in a really clean and modular manner. Plus you did some really great work with the custom theming functionality. Starred the repo and will definitively be sharing with some friends!
Soooo interesting ! thanks James !! I'm a begginer dev and, thanks to you, I created my own blog thanks to your react/velite/mdx tutorial 😍 I really love it !
Most of the components of Shadcn/ui are built on top of RadixUI (headless component library), which has the same advantagens as react-aria and respects accessibility as well.
Radix is a great library and I have used that for a while. Devon the creator mentioned that the biggest difference between React Aria and most other libraries in regards to accessibility is support for mobile screen readers. The ARIA Practices Guide doesn't cover those, so any library that purely bases their implementation on it will miss some important functionality. This combined with the features like renderProps, means I prefer React Aria Components now. But you cant go wrong with either.
Doesn't NextUI also use react aria under the hood? Though i think is not as lightweight as the options you mentioned since it also uses framer motion for some animations.
Monitor is a standard LG 1440p one. Its probably because I have scaling set to 175% when I record, so everything is larger and more readable on mobile devices.
great video, thanks! i was sold when you showed classNames styling the component - it annoys me so much in shadcn that a className won't override a variant - and you can't even move the className outside of the variant function (inside the cn function) to force it to. how does react-aria deal with styling table rows or other nested components? are they always flat(right term?) so you can add styles?
Will Adobe own anything we make with it? These are things we must know with Adobe doing what they are currently doing in the Year Of Our Lord Two Thousand and Twenty Four.
Its just the className prop, called Tailwind Fold (marketplace.visualstudio.com/items?itemName=stivo.tailwind-fold ) Useful when I want nice styled demos where the focus is not on styling.
why nobody talks about why you shouldn't use it? 1. styling 2. maintenance 3. time if you have a small project or a small team, DON'T use pure headless UI, go with something prebuilt like NextUI, Radix etc. Don't waste time on a custom styling, don't waste time on a maintenance and bug fixing. Time is money
I have used their non JS components for Tailwind examples before, not had too much interest in their JS stuff mainly because when I was looking at it it did not have many components. Seems quite built out now.
I really love the way you talk and explain. To the point, but not too fast. Very clear.
The topics are more advanced compared to 90% of dev youtubers, who seem to focus on very beginners almost exclusively. I like that you are not doing this.
One of the reasons I didn't want to use react-aria where changes like `onClick` to `onPress`. But your explanation made so much sense.
Keep it up dude, you are on the right track!
kskcnskncksn
lnvdln d
This is the best react-aria-components video I watched. Your examples for each features are absolutely wonderful. I will give a try your lib. Thank you.
damn I'm sold on the buttons 😆, who would have thought
I love React Aria's API. Simple and intuitive.
is it though? 5 hours later I'm still struggling to implement a ToastProvider. their typescript examples are weak at best imo. i want to love it, but man is it making it hard.
Excellent work man, thank you for making this!
Been building out a design system using the react-aria components with the tailwind-variants library and your codebase is a really great reference for how to do this type of thing in a really clean and modular manner. Plus you did some really great work with the custom theming functionality. Starred the repo and will definitively be sharing with some friends!
Soooo interesting ! thanks James !!
I'm a begginer dev and, thanks to you, I created my own blog thanks to your react/velite/mdx tutorial 😍 I really love it !
Awesome to hear about the blog, thanks for the kind words!
wow, it is so much amazing than i expected. radix should implement this more. i really like the functional className concept, very nice DX.
Thanks for sharing James
Beautiful api. Shadcn gets the press but I find it very convoluted, definitely skill issues 😆
Most of the components of Shadcn/ui are built on top of RadixUI (headless component library), which has the same advantagens as react-aria and respects accessibility as well.
Radix is a great library and I have used that for a while. Devon the creator mentioned that the biggest difference between React Aria and most other libraries in regards to accessibility is support for mobile screen readers. The ARIA Practices Guide doesn't cover those, so any library that purely bases their implementation on it will miss some important functionality.
This combined with the features like renderProps, means I prefer React Aria Components now. But you cant go wrong with either.
Doesn't NextUI also use react aria under the hood? Though i think is not as lightweight as the options you mentioned since it also uses framer motion for some animations.
Which monitor is you are using? Is that 4k? The font rendering is so smooth.
Monitor is a standard LG 1440p one. Its probably because I have scaling set to 175% when I record, so everything is larger and more readable on mobile devices.
great video, thanks! i was sold when you showed classNames styling the component - it annoys me so much in shadcn that a className won't override a variant - and you can't even move the className outside of the variant function (inside the cn function) to force it to.
how does react-aria deal with styling table rows or other nested components? are they always flat(right term?) so you can add styles?
also, how have you only got 4k followers?
Wow, I’ll try ❤
great video
Will Adobe own anything we make with it? These are things we must know with Adobe doing what they are currently doing in the Year Of Our Lord Two Thousand and Twenty Four.
It's Apache 2.0 licence, which allows private use, public use and commercial use. You just need to make your project also Apache 2.0 licenced
@@LukeWatts85not good
licence
adobe is associated with it
What's the extension which folds the props into a "..." ?
Its just the className prop, called Tailwind Fold (marketplace.visualstudio.com/items?itemName=stivo.tailwind-fold )
Useful when I want nice styled demos where the focus is not on styling.
Thank you for a video , (how did you centered this div hhhh kidding 😂)
why nobody talks about why you shouldn't use it?
1. styling 2. maintenance 3. time
if you have a small project or a small team, DON'T use pure headless UI, go with something prebuilt like NextUI, Radix etc. Don't waste time on a custom styling, don't waste time on a maintenance and bug fixing. Time is money
flowbite-react
Nah
I have used their non JS components for Tailwind examples before, not had too much interest in their JS stuff mainly because when I was looking at it it did not have many components. Seems quite built out now.
@@dkr91 explain sir , you can't just go leaving a "NAH"
Nice library but f*ck Adobe.