Tailwind is definitely my go to right now over all the other libraries out there. I agree that it is so easy to design with Tailwind. I also like their UI. Thanks for the great content Harry. See you soon!
I wanted to say thank you for making that last video because it pushed me to do a UI rework for my school project. It looks sooo much better. Thank you for the reminder to use tailwind!
Holly molly.. that's a LOT of class names. And I hate class names. As a styled-component user that looked insane. I really enjoy my className-free world! But I guess every tool solves a different problem. Nice video review!
This was really great. I have been on the fence with learning Tailwind, and I think this pushed me over the edge. Do you still find that you need something like Chakra to do more complex components like Tables, Modals, and Notifications?
As a SPA developer, still not sold. Css-in-js, preferably build time generated >>>>> anything else. Unless im doing mvc template engine based SSR then yes, tailwind as a replacement for bootstrap is ok.
Also, ironically, they taught the lessened overhead of inventing class names, and then they introduce @apply which is basically doing classes for classes?
Your last video made me try TailwindCSS. And your arguments comparing Tailwind with regular css files are correct. But how it compares to css-in-js solutions, like styled-components for example. Before Tailwind, I was using styled-components in all of my projects. Here are my 2 cents on it. 1. In your last video, you mentioned that tailwind code becomes more readable once you actually knows the classNames. But still, it takes more mental energy to get a clear picture of the code as compare to any css-in-js solution. Eg -> In tailwind- you will write something like .... while in styled-components, we will write ... Which make it more clean and more readable at just glancing the code.
As a backend developer, Tailwind helped me to do the styling without a need for frontend developer help since I don't need to bother CSS/styling definitions anymore. Just need to look up at the Tailwind docs (which is intuitive) for reference then styling would be a breeze. Having several classes at an element would be awkward at first, but I already got used to it. if you want to reuse then create a component instead.
One more thing is - when making reusable components especially the ones whose styles you want to change on certain props, like . Doing this in styled-components feels much easier. because you need another library "classnames" to easily change classnames
Never use @apply it's an anti-pattern and should not be used with atomic CSS. Instead, make the entire Button component reusable as he did before extracting the classes to the .button-green class!
Why bother with tailwind if you are going to abandon atomic css. Its like when react hooks came out they 100% recreate react class state with hooks. And put entire state into single hook. Power of tailwind is utility first framework and don't try to group it.
Thanks for the video, but ... writing a line of 60 to 100 chars, with 5 or more "new" classNames just for styling a h1 , paragraph or a button !!!... and the "@apply" command sends you back to CSS in a separate file, just like "classic" CSS. I can't see any benefit of using Tailwind in readability of for maintenance.
However, Tailwind is really best when it comes to spacing, or built-in color palette. This is really great as you don't get this in any css-in-js library
How about using an existing framework like Material UI and combine it with Tailwind for custom adjustments? How about using Styled Components with Tailwind?
There is a good reason why code should be separated from layout - - - be it css or php or whatever - - - The market wants you to know css2 and css3 for the client so a pool of coders in a company can maintain the code in the same assets. They don't want another set of classes to fill up the html. This only works for freelancers where the client doesn't have a clue.
Come on, global changes are the scariest thing in css? Yeah, if you have poor skills in organising your project and use classes without understanding. If you're still scared use BEM. Anyhows, good luck changing that padding on billions of elements. You need to change you're method of developing web, not the framework.
😂😂 14:30 push me and then just touch me till i can get my 😂😂😂🕺💃🕺💃 satisfaction lol ... what a song lol you brought me 10 years ago
Hahaha so glad you caught that
Tailwind is definitely my go to right now over all the other libraries out there. I agree that it is so easy to design with Tailwind. I also like their UI. Thanks for the great content Harry. See you soon!
I wanted to say thank you for making that last video because it pushed me to do a UI rework for my school project. It looks sooo much better. Thank you for the reminder to use tailwind!
Try it while watching TV!
ur awesome. more tailwind PLEASE
More Tailwind videos please!
Great content thanks! Maybe a quick demo in the intro ?
Holly molly.. that's a LOT of class names. And I hate class names. As a styled-component user that looked insane. I really enjoy my className-free world! But I guess every tool solves a different problem. Nice video review!
This was really great. I have been on the fence with learning Tailwind, and I think this pushed me over the edge. Do you still find that you need something like Chakra to do more complex components like Tables, Modals, and Notifications?
As a SPA developer, still not sold. Css-in-js, preferably build time generated >>>>> anything else.
Unless im doing mvc template engine based SSR then yes, tailwind as a replacement for bootstrap is ok.
Also, ironically, they taught the lessened overhead of inventing class names, and then they introduce @apply which is basically doing classes for classes?
Your last video made me try TailwindCSS. And your arguments comparing Tailwind with regular css files are correct. But how it compares to css-in-js solutions, like styled-components for example. Before Tailwind, I was using styled-components in all of my projects. Here are my 2 cents on it.
1. In your last video, you mentioned that tailwind code becomes more readable once you actually knows the classNames. But still, it takes more mental energy to get a clear picture of the code as compare to any css-in-js solution. Eg -> In tailwind- you will write something like
....
while in styled-components, we will write
...
Which make it more clean and more readable at just glancing the code.
As a backend developer, Tailwind helped me to do the styling without a need for frontend developer help since I don't need to bother CSS/styling definitions anymore. Just need to look up at the Tailwind docs (which is intuitive) for reference then styling would be a breeze. Having several classes at an element would be awkward at first, but I already got used to it. if you want to reuse then create a component instead.
One more thing is - when making reusable components especially the ones whose styles you want to change on certain props, like . Doing this in styled-components feels much easier. because you need another library "classnames" to easily change classnames
Any react-query stuff coming up?
Try the Net Ninja's course
Please do a video about "Tailwind + Nextjs"
Tailwind is so good. Help me learn css properties, because of how the classes are named. I'm better with pure css now.
Yup it got me interested in css
Never use @apply it's an anti-pattern and should not be used with atomic CSS.
Instead, make the entire Button component reusable as he did before extracting the classes to the .button-green class!
Why bother with tailwind if you are going to abandon atomic css. Its like when react hooks came out they 100% recreate react class state with hooks. And put entire state into single hook. Power of tailwind is utility first framework and don't try to group it.
Thanks for the video, but ... writing a line of 60 to 100 chars, with 5 or more "new" classNames just for styling a h1 , paragraph or a button !!!... and the "@apply" command sends you back to CSS in a separate file, just like "classic" CSS. I can't see any benefit of using Tailwind in readability of for maintenance.
However, Tailwind is really best when it comes to spacing, or built-in color palette. This is really great as you don't get this in any css-in-js library
Try twin.macro
@@ethanliu4012 Looks great. Definitely try it
How about using an existing framework like Material UI and combine it with Tailwind for custom adjustments? How about using Styled Components with Tailwind?
`twin.macro` is the way to go if you're looking to use Tailwind with styled-components
Do you use any tailwind component library for react?
awesome video, is there an api that gives me the all TW classes?
14:31 😂
It's easy to get started with Tailwind, but how easy it is to migrate away from it?
I’d say about as easy as any solid BEM usage. It’s a matter of updating your HTML, no need to worry about anything else.
There is a good reason why code should be separated from layout - - - be it css or php or whatever - - - The market wants you to know css2 and css3 for the client so a pool of coders in a company can maintain the code in the same assets. They don't want another set of classes to fill up the html. This only works for freelancers where the client doesn't have a clue.
First!
Nop, even in this very constraint example, the number of class names in a tag is overwhelming for me.
That’s not what designing is. I guess what you meant is that Tailwind makes it easier to build a UI.
Come on, global changes are the scariest thing in css? Yeah, if you have poor skills in organising your project and use classes without understanding. If you're still scared use BEM. Anyhows, good luck changing that padding on billions of elements. You need to change you're method of developing web, not the framework.
Global changes are so hard