Комментарии:
What do you think about component libraries?
ОтветитьComponent libraries are almost impossible to customize.
ОтветитьUsing Radix UI with Tailwind. ❤ TailwindUI is cool too, but a bit lacking. However, I purchased it just to support the project.
ОтветитьShadcn seems like a good all round solution
Ответитьno way Jose!
ОтветитьI love using mantine, but wanting to start using thw nextjs app directory. So been switching to tailwind, unless there is a component library that works with the nextjs app directory
ОтветитьHello, is your browser Safari? I'm wonder how you customize it and how to have sidebar?
ОтветитьInstead of "Stop using tailwind" how about "Think before using Tailwind" or "Components are more efficient than Tailwind" which is something I agree with.
ОтветитьWhat are your thoughts on native web component libraries like shoelace and microsoft FAST compared to react based libraries for building long term design systems?
ОтветитьThank you!
ОтветитьI've heard libraries like Mantine don't work well with SSR. Any thoughts on this?
ОтветитьYou persuade our designers and I buy you coffee for a month. 🙄
ОтветитьMisleading thumbnail and title. Video is good though. Like it.
ОтветитьHoly. DaisyUI is literally what I was looking for and I had no idea it existed. Thanks.
ОтветитьEasy... headless components + tailwind. Best of both world's.
Ответитьtailwind headless daisyui
ОтветитьI use Tailwind because customising component libraries is pain in the ass. I rather create the components myself.
ОтветитьInteresting take. I transitioned off comp libs like mui & mantine to tailwinds / headless, plus daisy (just for the semantic colors and themes). True, can't throw together UI quite as quickly as w/ traditional comp lib, but have lot more flexibility and I in long run I spend less time because don't need to reverse engineer or workaround limitations each comp lib has.
ОтветитьI love mantine UI + tailwindcss😍
ОтветитьMy team has had great success combining mantine and tailwind. Any time we need to customize a mantine component we slam some tailwind classes in and they play super nicely most of the time.
ОтветитьI use MUI (material ui) for work and personal projects. It's well documented and imo easy to use. I've tried tailwindcss and I see why people like. I think I comes down to use case and personal preference. Chakra UI and Mantine UI are great component libraries also but I don't think they have been out as long as MUI. Anyways great video - I dropped a like. 👍
ОтветитьMy only problem with UI libraries is that if you come across companies that incorporated an old version and never bothered to update the project with the current UI version, it is a nightmare trying to update everything to the current state.
ОтветитьThe thing about component libraries is that they come with a bit of learning curve. You need to look at their docs more often than you'd have to if you were using tailwind because you can far more easily guess classnames rather than component names and their props. At the end of the day it comes to preference but learning new things never hurts to find what sticks the best.
ОтветитьHe has a point. Imagine you have a dateline and you are worried about the ui when important parts are not finished.
ОтветитьTwo reasons I use component libraries :1) it saves time. 2) I dont have a good taste for design. I remember back in the days when bootstrap was popular I created a landing page using pure css, I was very proud of my design, and another using Bootstrap . Showed to my wife to choose the nicest of them. She picked the Bootstrap one, said that it looked nicer, more modern, easier on eyes. After that I rarely used pure css for my projects
ОтветитьDaisy UI looks like Bootstrap with extra steps.
ОтветитьWe’ll I guess most of you guys, don’t have to deal with intricate designs. Designs that change completely the look and feel of a basic component. Designs that push design and user experience to the edge. In those cases, yes it’s only logical to have some libraries in your arsenal… but there are cases that the libraries won’t cut it.
There are libraries like radix, react-aria, headlessUI that offers you basic components and their functionality but they’re without styling. That way you get to author you’re styles with having to override a bunch of predefined styles.
If you're needing to use a library like Daisy to make Tailwind more manageable then JFC maybe Tailwind isn't a good solution.
ОтветитьWe settled on Radix UI + Tailwind. Good stuff!
ОтветитьUsing UI libs is only a pick when we have to deliver product pretty quickly or theres no budget for custom ui and even tho the only viable pick is mantine atm, MUI and chakra are pain in the ass, chakra is survivable yet, but MUI has the worst DX you could ever experience and the only value is that it gives hella alot of variants of x component and thats cool for customizing ui of an app with only "copy and paste from docs". Otherwise TailwindUI+RadixUi+Tailwind for customizing the components i dont see any better pick I would never use UI lib like mui, its catastrophic experience, but client doesnt care what you will use and what matters is the final results, so from business/company perspective who have a team of devs picking ui can be a good pick, but for somebody who wanna work on a single longterm product custom components and ui is the only pick.
I also hate UI libs overall, but I love tailwind and thats why i wanna build my own tailwind based ui lib to use it for my projects since im more focused on delivering functionalities these days than ui and how does it looks like
We use MUI (formerly Material-UI) as React Component library at work. I have a personal project that still uses Bootstrap (and is a mess). This video helped me learn about DaisyUI, Mantine, etc. It's difficult to decide if you don't know those libraries upfront. However, I'd always use a component library for the exact same reasons you have in your video. 😉
ОтветитьI am a tailwind purist, but I still liked and subscribed. TailwindUI templates + components have been pretty decent for me
ОтветитьI like chakra in general, I used it in one of the project. But lately it’s not compatible with in Next 13 inside app directory. 😢
ОтветитьAlso try headless UI with tailwind.
ОтветитьI NEEDEED THIS VIDEO LOL. I WAS JUST THINKING ABOUT IT
ОтветитьWhat about component libraries based on tailwind? Like daisyui
ОтветитьThe problem is that you will use enough time to modify those components
ОтветитьI really prefer using ui libraries one of my favorites is PrimeReact but when your manager says don't use libraries make everything by yourself you do everything by yourself,especially when the project it's too big everything matters especially for perfmonace reasons
ОтветитьGreat video. I thought you did a great job at balancing the landscape.
Is that excalidraw that you are using?
Super insightful - I am a Tailwind fan, however, I don't like how much they charge for their pre-build component library. I have never heard of DaisyUI and will definitely check it out ;)
ОтветитьI like to write my own components, and keep copying/pasting and improving them every time
Ответить