@@WebDevCody it's a component library much like MUI but the batteries included in this are very very impressive. And generally just easier to work with and customize.
I agree. Ever since I've first seen Mantine, I have been using it in every single project. It also has a ton of useful hooks, a notification system, a rich text editor and many others. All written in TypeScript and used through components instead of non-React classnames.
DaisyUI is great because it gives you reasonable defaults that are not components, just styles. Makes it so easy to start at a good baseline and then modify or override with more tailwind classes
I am excited for JoyUI. It is from the same developers that are making MUI but JoyUI is not connected to Google and their Material Design. I really recommend checking it out/following it a bit. It is currently still in alpha but I think the first full version is supposed to come out this year.
Interesting to see a component framework using tailwind. I am currently using chakra ui and tailwind for my project. Even thought chakra ui isn't using tailwind (I think so), it still works great together. The advantage I see in daisyUI is that you have a unique design system and that they suggest to customize their components globally using tailwind. I think this is also possible in chakra ui but not suggested and may lead to some weird behaviour.
Hello,I would use some help. After following all steps from daisy ui official site,and try to start my React project, get error: ode_modules\daisyui\src\index.js Unknown word (22:5) 20 | let logs = false 21 | if (config("daisyui.logs") != false) { > 22 | logs = true | ^ 23 | } 24 | if (logs) { Can someone help? :)
Sure, if you have the time and budget to do that, but this is for a side project so I don’t want to waste time with building styling if I don’t need to when starting off. If you need a complete custom ui and design, then you’d probably end up building your own components
I don't really get why people like tailwind so much. Especially, when you have a mock, which you "just" need to translate to HTML/CSS, tailwind in most cases feels more like a different way to use the "style" tag
when i study, we learn how to write tags with style build in tag. Before css a thing people use this tech, but its require more powerfull pc. In 2005 128mb gpu and 1gb ram is a beast pc, so this tech didn`t find usage.
daisyUI doesn't make sense. it defeats the purpose of using Tailwind anyway. I'd much rather create atomic components with my styles and use Headless UI for the more complex implementations.
Mantine, bro. That one is a monster. It gives MUI and Chakra a run for their money, probably the next big thing to take over. AND IT'S FREE!!
I’ll have to check it out
@@WebDevCody it's a component library much like MUI but the batteries included in this are very very impressive. And generally just easier to work with and customize.
I agree. Ever since I've first seen Mantine, I have been using it in every single project. It also has a ton of useful hooks, a notification system, a rich text editor and many others. All written in TypeScript and used through components instead of non-React classnames.
I use mantine for everything. Definitely the next big thing
Mantine looks good, but what's the difference between material UI / chakra ? If I'm not wrong Mantine does not support tailwind CSS like daisy UI.
DaisyUI is great because it gives you reasonable defaults that are not components, just styles. Makes it so easy to start at a good baseline and then modify or override with more tailwind classes
I am excited for JoyUI. It is from the same developers that are making MUI but JoyUI is not connected to Google and their Material Design. I really recommend checking it out/following it a bit. It is currently still in alpha but I think the first full version is supposed to come out this year.
seems like it has a lot of potential. Hope it releases a stable version soon. before that kinda have to avoid using it in alpha
Yesterday I was looking for tailwind components,
You came on time 👍
Interesting to see a component framework using tailwind.
I am currently using chakra ui and tailwind for my project. Even thought chakra ui isn't using tailwind (I think so), it still works great together.
The advantage I see in daisyUI is that you have a unique design system and that they suggest to customize their components globally using tailwind.
I think this is also possible in chakra ui but not suggested and may lead to some weird behaviour.
How about the performance? I was wondering my project will using tailwind + chakra ui too
Thanks for showing me this. I've been looking for similar.
Good job babe!!!
Daisyui is fun to use...
I've tried it before, I see its usefulness.
wow pretty interesting, thanks for sharing this
I've also used daisyui, and it's pretty nice. But recently I stumbled upon flowbite and now I'm thinking on switching 🤔
daisy ui is so good
Material ui is all time best
Amazing, my last two projects with daisyUI……thought it's not that popular……man
Do you still like it?
@@WebDevCody sure, easy to use and decent effect
Mantine is the best atm
Hello,I would use some help. After following all steps from daisy ui official site,and try to start my React project, get error:
ode_modules\daisyui\src\index.js Unknown word (22:5)
20 | let logs = false
21 | if (config("daisyui.logs") != false) {
> 22 | logs = true
| ^
23 | }
24 | if (logs) {
Can someone help? :)
So, this is bootstrap
Feels like it, but for tailwind css
@@WebDevCody its indeed like bootstrap. thats what a design system is :D
I always thought it was best to build everything out from pure css and no frameworks. Or am I wrong?
Sure, if you have the time and budget to do that, but this is for a side project so I don’t want to waste time with building styling if I don’t need to when starting off. If you need a complete custom ui and design, then you’d probably end up building your own components
I don't really get why people like tailwind so much. Especially, when you have a mock, which you "just" need to translate to HTML/CSS, tailwind in most cases feels more like a different way to use the "style" tag
when i study, we learn how to write tags with style build in tag. Before css a thing people use this tech, but its require more powerfull pc. In 2005 128mb gpu and 1gb ram is a beast pc, so this tech didn`t find usage.
@@Time2paw I think you wanted to post it generally, since it has nothing to do with my post, hasnt it?
daisyUI doesn't make sense. it defeats the purpose of using Tailwind anyway.
I'd much rather create atomic components with my styles and use Headless UI for the more complex implementations.