For beginners i would say not to touch Tailwind or Bootstrap when you are starting to learn. Write your own css to learn it first and then use frameworks so that you know what they do. The only reason i don't like ( like ) tailwind or bootstrap is that you are writing css via writing html and you will never learn the actual properties which does the magic :( . It doesn't mean not to use it, i have used tailwind for most of my personal projects and i love it ( because i know the css behind it )
CSS on its own is pretty frustrating. Tailwind just makes sense from the start. Everything is easy. Which I think is good for people just starting out. It makes work fun. I actually recommend the same for server side and client side frameworks. Just start with a framework. It makes it easier to pick up good habits, because the frameworks will tend to nudge you in the right direction.
@@aslamshah88i completely disagree. While you should learn basic css before learning tailwind, that all you need to know. Especially using vscode, tailwind has made me much better at writing actual css as it tells you the definition of each class in the bass css
@@rez188 What happens when you switch to a new framework or have to write custom css? Most of the utility classes have more properties behind them. If you get use to the utility classes, then one might forget about the real properties ( in long run ). Also i mentioned in my comment "For beginners " but if you already know the magic behind it then it should be good to go. Personally for me after using TL on many projects, i struggle a bit when i have to write pure css :)
I really love how this story feels so natural to hear, I've been using and following TailwindCSS from the early days, and I can surely say that it blew my mind right after the very first moment.
Writing CSS is one of the annoying things to do when developing the web. CSS Framework only helps for the start of the development but when your team is growing, it's getting harder to maintain the CSS code, The bundle becoming more bigger, and more time to develop the UI. TailwindCSS is the one of biggest game changer for the web development today. Making easier and faster for developers to modify the UI, optimizing performance, teaches a lot of things that new developers don't know in CSS that might be done, and easy to share easily modifiable code like TailwindUI and Tailwind Components. I used to love CSS and it's Pre-processor like SASS or LESS, but I was often limited by time and the difficulty of building something from scratch. With TailwindCSS, now developing the UI is more easier and very fast. It's impossible for me to switch from TailwindCSS to the old way at this rate.
What made me love Tailwind was when I converted a small bootstrap page to tailwind and the css file was 17kb instead of 150kb because of bootstrap (I know I could optimize it, but I didn't knew back then)
Nobody : I have an urge to write inline styles because I want the layout to be completely unreadable while also making it a nightmare to maintain or update in a centralized manner, but I'm ashamed to write inline styles because it's considered a bad practice. Tailwind Creator: Say no more fam!
That's how truly great products are made - organically, naturally, unplanned
Imagine doing this within some Scrum framework with some PO or Scrum Master breathing down your neck and tellig what to work on next 😅
Tailwind is one of the best things to happen to css in a long time
no :-)
For beginners i would say not to touch Tailwind or Bootstrap when you are starting to learn. Write your own css to learn it first and then use frameworks so that you know what they do. The only reason i don't like ( like ) tailwind or bootstrap is that you are writing css via writing html and you will never learn the actual properties which does the magic :( . It doesn't mean not to use it, i have used tailwind for most of my personal projects and i love it ( because i know the css behind it )
CSS on its own is pretty frustrating. Tailwind just makes sense from the start. Everything is easy. Which I think is good for people just starting out. It makes work fun.
I actually recommend the same for server side and client side frameworks. Just start with a framework. It makes it easier to pick up good habits, because the frameworks will tend to nudge you in the right direction.
@@aslamshah88i completely disagree. While you should learn basic css before learning tailwind, that all you need to know. Especially using vscode, tailwind has made me much better at writing actual css as it tells you the definition of each class in the bass css
@@rez188 What happens when you switch to a new framework or have to write custom css? Most of the utility classes have more properties behind them. If you get use to the utility classes, then one might forget about the real properties ( in long run ). Also i mentioned in my comment "For beginners " but if you already know the magic behind it then it should be good to go. Personally for me after using TL on many projects, i struggle a bit when i have to write pure css :)
I really love how this story feels so natural to hear, I've been using and following TailwindCSS from the early days, and I can surely say that it blew my mind right after the very first moment.
Thank you Adam, and the whole team. Tailwind is a joy to work with and it's actually taught me tons about CSS in general. 🙏
Writing CSS is one of the annoying things to do when developing the web. CSS Framework only helps for the start of the development but when your team is growing, it's getting harder to maintain the CSS code, The bundle becoming more bigger, and more time to develop the UI.
TailwindCSS is the one of biggest game changer for the web development today. Making easier and faster for developers to modify the UI, optimizing performance, teaches a lot of things that new developers don't know in CSS that might be done, and easy to share easily modifiable code like TailwindUI and Tailwind Components.
I used to love CSS and it's Pre-processor like SASS or LESS, but I was often limited by time and the difficulty of building something from scratch. With TailwindCSS, now developing the UI is more easier and very fast. It's impossible for me to switch from TailwindCSS to the old way at this rate.
Dev community needs more content like this ❤️🙏🏻
What made me love Tailwind was when I converted a small bootstrap page to tailwind and the css file was 17kb instead of 150kb because of bootstrap (I know I could optimize it, but I didn't knew back then)
Tailwind will be here for a long time - great work and much appreciation for the great people at tailwind
using tailwindcss since v1 and it has improved a lot.
Great content thank you so much!
I'm a hardware engineer Transitioning to software. This and Typescript documentary were very helpful
Wonderful video! Could you decrease the background music in future ones? I felt it was a bit too loud here
Lots to learn from this story, thanks Adam
Thank you again! didn't even know about this one, my YT feed is scary and awesome.
Nobody : I have an urge to write inline styles because I want the layout to be completely unreadable while also making it a nightmare to maintain or update in a centralized manner, but I'm ashamed to write inline styles because it's considered a bad practice.
Tailwind Creator: Say no more fam!
I love this one guys! thank you for it. Would have loved some cutaways of the CSS etc. anyways, good job.
I love Tailwind and use in all my projects!
Thank you.
Declarative css FTW
Tailwind is cool, but the 1/3 side angle camera perspective was terrible lol
What a cool channel.
Cause Tailwind is awesome and removes all the complexity of responsive design and a million files just to do a simple thing
I like tailwind really greate thing
tailwind makes me like css like jquery made me like javascript
I hated bootstrap cuz I could not pick a color for the button out of the box.