Hey Diego, thanks for watching! Completely valid question. One of the main reasons is that the Radix UI has a bit of a different Typography system compared to something like Tailwind CSS Typography (tailwindcss.com/docs/typography-plugin ). It is mainly just a preference from which one you prefer from a design perspective. Some differences are that Tailwind CSS Typography has size options 1-5, while Radix UI Themes typography has size options 1-9. Radix UI Themes maps each size to certain attributes (Check it out here under Type Scale: www.radix-ui.com/themes/docs/theme/typography#type-scale ). So when you use the Text / Heading components you can then adhere to this Radix UI Typography sizing system, instead of the Tailwind CSS Typography system. All in all, it is optional but recommended to keep design of text consistent across your application, you can technically just be very diligent and manually write sizing with Tailwind alone but the Typography system from Radix UI just helps simplify things. Hopefully this helps and is not too verbose :) thanks again for watching.

Hahaha maybeee based off real experience :), thanks for watching!

Thank you for watching :). It can definitely be weird to put layout styles as component props, and honestly it was a bit strange at first. There are pros and cons to using something like this framework instead of just using the regular Tailwind CSS frameworks, but Radix UI Themes has a really interesting way of implementing breakpoints that is worth looking at. www.radix-ui.com/themes/docs/theme/breakpoints Check out the documentation above, you can create different values at certain breakpoints for any attributes. For example, with a Flex container you could do something like This can be seen as verbose, but I believe can allow for readability as opposed to using the inline Tailwind CSS ways of allowing for different flex values at different screen widths. Just thought I'd show that Radix UI Themes does have a way of addressing responsive layouts. Again thank you for watching.

Thank you for taking the time to watch my video :). I personally found the setup / component download process of shadcn/ui tiring, and I've done a video covering shadcn/ui in the past. I do think shadcn/ui is a great option and you should choose whatever you're most comfortable with. I do believe there are solid benefits to be had when it comes to using something like a Flex component instead of a div with className="flex". I want to again emphasize that you are going to structurally get the same exact result, so choose what you are most comfortable with. Benefits of Flex component over div: * When quickly reading code, you can understand your overall layout more easily. Instead of seeing "div div div div" you can instead see "Container, Flex, Grid" etc. so it makes code more readable at a glance. * The attributes in a flex component are easier to read when compared to long lists of classes (in my opinion), I prefer something like over . This is simply preference, and if you prefer tailwind alone then I suggest to do such. Outside of the two points above, it really is just preference. Again thank you for watching