Apparently, Kevin, you're also the second most popular source of leads for the State of CSS, besides the State of CSS itself (see Demographics > Source). Thank you for all the videos, always entertaining while being very educational.
Nice to know that the extreme noise surrounding Tailwind on social media doesn't necessarily represent real world usage... The love/hate aspect of anything spreads like wildfire on social media. Those algorithms just love us arguing with each other 😂 Lot's of other very interesting insights here, especially if you're an advocate for #a11y… Sad to see the low numbers regarding testing, but reminds us all to ensure we keep sharing our knowledge around in this aspect.
Every 2 weeks or so I visit css tricks just in case by chance they’ve made a post again, and every time I seriously feel like crying. It makes me so sad that they killed it off suddenly and without explanation. It’s the main thing that inspired me to love CSS and I’d spend every morning reading the latest posts while I had my coffee. It was so helpful to my career but more than that it just felt like a safe place to me where there were people like me talking about how to do cool things. Every time I visit I hope that just maybe they’ve posted **anything**, but it’s a graveyard. And that makes me tear up.
I could be wrong, but I'm pretty sure they've officially stopped bothering with it, sadly. Like you said, it was such an incredible source of knowledge and inspiration, and it's mind blowing how fast they managed to kill it.
@@KevinPowell isn't part of it got to do with their first tweet after they bought CSS-tricks? it was about promoting the font-size: 62.5% thing "to ease calculations with em/rem"
The reason i voted for you in this survey was not due to you being the "face" of web devs or whatever on youtube, but because out of every youtuber i have ever tried learning css from, you explain things in just the right way, you are like the perfect teacher for anyone wanting to learn css, your videos may or may not make people the best in the world in css or whatever, but you definitely get people far. you are literally the reason i am good at css and html right now. anyways i just wanted to say this because i believe it to be true :)
I think that Tailwind CSS may not be the best choice when working with a CMS like WordPress. In such cases, I prefer using vanilla CSS for CMS templates. However, Tailwind CSS is excellent for React apps or websites.
My approach to screen readers is to have a very clean accessibility tree on chrome devtools and everything usable by keyboard. I only fire up VoiceOver sparingly to double check, but I've never seen that fail.
I've fully gone over to using Tailwind now. It's made me much faster and it's so much easier for editing existing components. BUT I can't believe anyone could make good use of it if they don't understand the underlying CSS. Everytime I type in a tailwind class I'm imagining in my head the CSS it is representing (or, if I forget, allowing VS Code to tell me with a tooltip) so I can still comprehend how things will cascade and inherit. And for more complicated circumstances one still has to be able to roll your own CSS (for some funky grid setups, for example).
This all works great until there are hundreds of css files with dozens of developers working on a large project then writing css natively doesn't scale at all
I would love to see you recreate components from TailwindUI in vanilla CSS! Also, to cover and give your thoughts on Refacting UI. Just discovered Tailwind CSS I gotta say it's pretty slick as a design system. Took me a while to wrap my head around TW CSS and frameworks in general. I think theres a severe lack of videos covering the basic concepts of how these frameworks... work and how to use them explained in simple basic terms. For someone new to them it's really confusing. Also, a good video would be on how to make your own framework based around your own personal style. Always look forward to your new videos!
12:19 Subgrid, :has and container queries are the main features I would like to use, but I don't because the browsers support is not ideal yet, It is good to see I'm not alone
Yeah :/. But at least there are still lots of useful articles we can read. I also often find them when I search for something. So the project is not really dead, it's just frozen, I would say.
On the topic of Tailwind, I am definitely in the it's not for me camp. I have tried it, I am even using it in a current project and I feel like tailwind cannot replace plain css, at least not completely. I constantly run into things that I want to do that I could do in css, but in tailwind is not possible or it would be too hard to read all the classes or people are just saying do it with javascript.
First things first. I'm doing the Odin Project, and watching your videos... thanks a lot. I'm 56, no more time to lose. Now, a point of view I would like to share. It's a kind of easy to play guitar, but those who understand music theory have much more insights, or material for creativity, due to that. I really will learn the root thing before easy my way with these tools, due to that. Tools do not provide creative thinking, problem-solving thinking.
So well deserved that you are number 1 of the people we follow for CSS 🙌! I learned a LOT of modern and advanced CSS from your videos, and I just love how you present the content. Even for simple concepts you always provide additional background info - showing that you did a lot of research. I appreciate it very much that you share all this knowledge with us! 🤝 And on top of that, you are just such a nice guy ❤. You just proved it again by your humble reaction to the result of the survey. So many reasons that I don't miss a single of your videos. 🚀
I still use Sass a lot, not with every project, but quite a bit. I'm in the boat with you though when it comes to not using TailwindCSS, I'm just personally not a big fan of it.
im working on a new css framework right now 😅 and the state of CSS survey has given me a ton to learn about on this journey. it's fantastic to see the CSS community bustling with ideas and modern approaches to web development. gives me a lot to do!
I know i'm about a year late in watching this but I think it's important to understand that UnoCSS is largely a drop in replacement for TailwindCSS (if you use the default settings) but goes a bit further in allowing you to create your own grammars/rules/etc. In a way -- though it's definitely an imperfect comparison -- it's like JS and TS being considered different languages when compared against other languages. It tries to distinguish these two flavors but in doing so reduces the overall dominance that JS/TS and Tailwind/Uno have in the space they occupy.
I didn't read through all of the above comments, but I love working with Tailwind as well as working with vanilla CSS and SASS. That being said it is important to know how to use CSS before reaching for Tailwind. I simply view Tailwind as an alternate way to apply CSS. Maybe the thing I like most about Tailwind is the configurable design system out of the box (and tree shaking).
I wished I knew about the survey, I feel like I also miss these kinds of things 😅 Subscribed for the newsletter now, maybe I'll be able to take part next year
CSS frameworks have come and gone over the almost 2 decades Ive been working with websites and I have dipped my toes (well, actually for a few instances deeper than that) but I always find myself relying more and going back to just pure CSS. Theres a certain amount of peace of mind that although frameworks trends rise and fall every day, you can always be sure to rest on the foundation of knowing how to create and edit clean and lean pure css.
I see the advantages of using Tailwind but i simply cannot make myself write such bloated html. I prefer to focus on writing minimalistic and efficient css.
17:03 this seems like a bug in the survey. ":has" is shown as most adopted, but then text below talks about gap support for flexbox. It looks like only the comments award is shown properly.
I am a fan who honestly, also wishes you also make tailwind content. I always re-implement the design ideas I learn from you into tailwind so I feel there is more similarities and that much divide.
And i mean that seriously, its to the point that i wish there was someone on the internet just as good as you at teaching and being entertaining in javascript instead of html and css. In fact please do let me know if there is anyone you know of that you think is great at teaching javascript whether it be in text or video form. (As you probably can tell i value your opinion very highly...)
Congrats on being no #1 ! Also, Panda is used to convert sass,scss to css on early days before ruby scripts and VSCODE extension which in most cases deprecated by new tools
I'm really curious if there's any correlation between React and Tailwind usage. It always feels like people only like Tailwind because React doesn't really allow styled components unlike other frameworks.
I hire/manage product teams, and I wouldn't bring in an external team without using tailwinds. It's ok to have custom css but for maintainability, bringing in new devs, and long term maintenance I think tailwind css is great.
Tailwind. Hmmm... that's a contentious one, eh? I'm old school, and have always hand-written my own CSS (using OOCSS/SMACSS/BEM methodologies, etc), creating components/legos. I personally hate Tailwind. I had to use it in 1 project, and it killed me a little every day. But... I do understand why some people love it, especially if they're not so well versed in the nuances of CSS (i.e. cascade/inheritance/specificity).
Agreed 100%. That's the problem that CSS needs to fix, IMO. I've solved it with using SCSS modules (e.g. Component.module.scss), requiring me to name my CSS class exactly the same as my component. And, like Kevin, I simply select my nested HTML elements (semantics matter!) instead of coming up with more class names. When CSS supports proper scoping (work in progress) I'm sure it'll take a turn for the better. For now, only web components can scope CSS to a single component using vanilla HTML/CSS. Unless you use pre-processors like SASS and (S)CSS modules.
I personally hate it too, I think it’s an abomination. IMHO it was designed for JavaScript nerds who don’t know how to design anything. That said I don’t use any frameworks unless I have to, I use my own custom tools built with Sass so idk. 🤷♂️
@@mahadevovnl I've recently used Astro on a couple of small projects, and I used a mix of "global" CSS/Sass partials for setting up custom properties / reset / typography / grid system, then locally scoped "inline" CSS inside the Astro components. It worked really well.
To be honest I kinda do like Tailwind and I do understand CSS nuances you mentioned and in the past I've used many CSS methodologies you mentioned in your comment. I think it's bad to generalize like this implying "Tailwind is used by developers that don't know CSS". You cannot really use Tailwind if you don't know how to use CSS. As with everything else in programming, it's just a matter of tradeoffs. I wouldn't use Tailwind for a landing page or a simple website with few pages. On the other hand if I'm working on some modern component based application, then it's definitely a good candidate for a project.
@@rand0mtv660 The point with "You cannot really use Tailwind if you don't know how to use CSS." is that if you knew CSS, you would use CSS. Those who default to TW don't know CSS (also in my experience interviewing many people) and they make a huge spaghettified mess of it. TW is tech debt from day one, a complete vendor lock-in, and is full of anti-patterns. My guess? Five years from now, as CSS keeps evolving, TW will be a thing nobody likes or wants to work with anymore (like Bootstrap has fallen out of fashion, which is much less opinionated and divisive) and, well, good luck finding people to help you maintain your monstrosity of an app with 10+ to 20+ or even 40+ of utility classes in every single HTML element in your ENTIRE app. It's not future-proof. Saying "TW is CSS" is just a way of saying: "I don't know what I'm talking about." I'm seriously astonished at how many people like something this stupid :D
First of all great channel...The answer to the question is; most likely. But there is no greater mark on a design process and outcome then the creativity inspired by vanilla CSS. Although Tailwinds does leave room for some ingenuity, I find it's like working with another artists' brush. CSS is the art work, not the framework.
Hi I try to make personal projects and struggle with picking colors. What rule should I follow maybe make new video on this topic since you are the best thanks!
Ive tried to get into Frameworks a lot, because it always felt like people who take webdesign seriously use css frameworks. But always out of like "obligation". But honestly, after like 15 years, I'm gonna stand up and say it: Pure CSS is very writable, you don't need a framework to make your life easier here. Especially if you go for smart, minimalistic solutions. I'd say you even come out on top if you count all the setup and the compatibility issues created by switching other frameworks in your project. Pure CSS just works and you can slap open the dumbest text editor and fix a small problem in a minute instead of going through all the overhead created by the framework. The lot of them feel like taking your car out for a 200m drive to the supermarket instead of walking.
Not really like those CSS framework (Tailwind, Bootstrap etc.) What I think is..the time I spend on searching relevant classes to apply the style is too much, where I just need a couple of seconds to apply the style if I type the CSS out. Beside, I just don't like the HTML DOM look so mess with so many classes..
tailwind is fine, but it isn't a silver bullet. i still find writing stylesheets to be very enjoyable although using tailwind or similar tools for quick projects is still awesome.
For CSS in JS solutions they're all dropping significantly on new project because they require a runtime on the client side to work, and with the last version of React and server components all the styling is computed serverside (or you have to disable server components which has a high negative impact on perfs).
Sir I am new frontend developer and I use simple css. I was thinking of learning tailwind.Can you help me in what css library i should learn to grow more
If I learned a language it would be Tailwind or PurgeCSS. Because these aren't loss poularity like a Bootstrap (I think bootstrap populartiy loss 20% beetween 2019-2023.). I wonder your opinion. suppose If you going to learn which one would you choice? Thanks your answer Kevin.
I use Tailwind and CSS together. I see them as having different use cases. Tailwind is for quick and dirty inline styling wheras css is for more detailed abstracted styling. I never knew Tailwind was so popular, I thought it was a niche Laravel thing. I think it will have its moment in the sun and then fade away - like jQuery. jQuery used to be a must have skill then Node and Vue / Angular etc. came along and people started getting back into raw JavaScript again. CSS frameworks and libraries are the same. They will fall in and out of fashion but there will always be base CSS. I only use Tailwind because its now part of the Laravel framework. I never liked Bootstrap - I either call it 'Poopstrap' , 'Bloatstrap' or 'Blandstrap' in my head. I prefer Tailwind because its more flexible and doesnt force you to write confusing layouts with loads of nested elements. As CSS is evolving at such a pace into such an awsome language I only regret not having enough time to faliarising myself with its new features more because those make learning new css frameworks and pre-compilers increasingly pointless.
The reason tailwind usage slopes like that vs retention is because it's been shoehorned into so many projects that need to make a quick prototype to demo the core of the project. Since the projects goal isn't CSS they reach for token based styles to make something quick forcing a lot of downstream consumers to be convinced they also HAVE to use it to build on top of the starter code. Similar in effect as bootstrap leaking into everything in 2011+ but with much heavier network-effects pushing hype-awareness and forcing usage in the current web vs how frameworks propagated a decade ago when bootstrap came out. Then retention kicks in as downstream consumers of those projects start hitting the problems caused by using something like tailwind when you aren't prototyping or a large distributed team. But the retention doesn't nosedive because have you ever had to gut a token system out of a component project. Web-development tooling is broken.
I think TailwindCSS vs. Bootstrap. You either use one or the other at your job and most likely hate the one you have to use due to the previous Devs thinking something about it that they should not have. Like they wrote "!important" to overwrite something they 100% did not need to. For testing why test on things other than desktop/laptop, if you only have to support them (work-related internal applications). I would say still test on different widths which I see people do not and some of the sites look bad even at max 1920px.
In UX that !important issue is known as a Desire Path. These indicate flaws in the UX of a system. (The classic example is dead grass where people walk instead of walking on the designed path.) The underlying problem with all of these frameworks is that they trade off flexibility for usability. That works great when you're starting out or working together with people on a big project, but creates impedance for people that know the underlying technology. So, they find "creative" ways to work faster, creating unintended knock-on effects. You can't _control_ human nature. You have to design around it. This is the lesson of Desire Paths. You can't just tell everyone not to walk on the dirt path everyone prefers. You can't moralize the issue away.
I do not disagree with you in general. It seems to me it is a lot of a lack of understanding though. Meaning 9/10 times you can just remove the "!important" and nothing changes. Also in both Bootstrap and TailwindCSS, there are better ways to change most of the defaults in their controls just requires develing more than a minute into the library.
I tried creating a pet project with Tailwind to learn it and as I added more and more functionality tailwind in my Vue templates became unreadable. So good for quick, bad for big
Scrollbar styling is far from being in a good state. Not only do we not have a consistent cross-browser solution, the solutions that do exist don't even work the same across platforms. Even after 15 years of working, this is something that can only be solved in JS...
Would you write like this in JavaScript: document.writeln(""); document.writeln("..."); document.writeln(""); No matter your level as a frontend developer, you will inevitably be disgusted by the above method of writing.Similarly, why is the concept of: class="inline-block bg-gray-200 rounded-full px-3 py-1 text-sm font-semibold text-gray-700 mr-2" Why is it revered? Both are essentially hardcoding in the wrong way. The concept is identical in both instances. CSS can certainly be described with any tool, and no one would complain about that, but you should not describe CSS in the worst possible way.Then you tell me how excellent Tailwind is. If you think Tailwind is so great, then doesn't the practice of document.writeln(""); also become excellent? Those who like Tailwind always like to criticize other CSS frameworks, which I think is just arguing for the sake of arguing, and it's meaningless.Tailwind claims high development efficiency, and admittedly, this is true, but it brings about management hurdles and a learning curve. The author of Tailwind provides corresponding solutions and tools, which, ironically, prove that what you develop yourself can cause many problems; otherwise, why would a simple CSS need so many tools for optimization? Stop fooling yourself here, Tailwind is just a terrible product of the times.
I don't want to live in a world where Tailwind has taken over, because I've been there, it's called the 1990s, when every style was inline and there was no separation of concern and no semantics in styling. It blows my mind that people are flocking back to this incredibly bad way of representing styles, but herd mentality is what it is.
Apparently, Kevin, you're also the second most popular source of leads for the State of CSS, besides the State of CSS itself (see Demographics > Source). Thank you for all the videos, always entertaining while being very educational.
well, that explains why he would be on top of "who you follow"
Kevin is also insanely good at css. He understands it way better than I will ever.
Who is the other one you follow?
Congrats Kevin on being #1. Well deserved!!!
Nice to know that the extreme noise surrounding Tailwind on social media doesn't necessarily represent real world usage... The love/hate aspect of anything spreads like wildfire on social media. Those algorithms just love us arguing with each other 😂
Lot's of other very interesting insights here, especially if you're an advocate for #a11y… Sad to see the low numbers regarding testing, but reminds us all to ensure we keep sharing our knowledge around in this aspect.
Every 2 weeks or so I visit css tricks just in case by chance they’ve made a post again, and every time I seriously feel like crying. It makes me so sad that they killed it off suddenly and without explanation. It’s the main thing that inspired me to love CSS and I’d spend every morning reading the latest posts while I had my coffee. It was so helpful to my career but more than that it just felt like a safe place to me where there were people like me talking about how to do cool things. Every time I visit I hope that just maybe they’ve posted **anything**, but it’s a graveyard. And that makes me tear up.
I could be wrong, but I'm pretty sure they've officially stopped bothering with it, sadly. Like you said, it was such an incredible source of knowledge and inspiration, and it's mind blowing how fast they managed to kill it.
@@KevinPowell
isn't part of it got to do with their first tweet after they bought CSS-tricks?
it was about promoting the font-size: 62.5% thing "to ease calculations with em/rem"
The reason i voted for you in this survey was not due to you being the "face" of web devs or whatever on youtube, but because out of every youtuber i have ever tried learning css from, you explain things in just the right way, you are like the perfect teacher for anyone wanting to learn css, your videos may or may not make people the best in the world in css or whatever, but you definitely get people far. you are literally the reason i am good at css and html right now. anyways i just wanted to say this because i believe it to be true :)
same here. Gracias Kevin!
I think that Tailwind CSS may not be the best choice when working with a CMS like WordPress. In such cases, I prefer using vanilla CSS for CMS templates. However, Tailwind CSS is excellent for React apps or websites.
My approach to screen readers is to have a very clean accessibility tree on chrome devtools and everything usable by keyboard. I only fire up VoiceOver sparingly to double check, but I've never seen that fail.
I've fully gone over to using Tailwind now. It's made me much faster and it's so much easier for editing existing components. BUT I can't believe anyone could make good use of it if they don't understand the underlying CSS. Everytime I type in a tailwind class I'm imagining in my head the CSS it is representing (or, if I forget, allowing VS Code to tell me with a tooltip) so I can still comprehend how things will cascade and inherit. And for more complicated circumstances one still has to be able to roll your own CSS (for some funky grid setups, for example).
I did use Tailwind for a while but I went off it. Too much HTML and classes to remember. Much prefer writing CSS intuitively.
Indeed, just use emmet if writing props feels slow.
Just build tailwind html blocks into components for better maintainability
This all works great until there are hundreds of css files with dozens of developers working on a large project then writing css natively doesn't scale at all
@@HorizonHuntxr I don't have dozens of developers working for me so my preferred method works well for me and my clients.
Many classes to remember? They are literally the names of the css properties 🤨
I would love to see you recreate components from TailwindUI in vanilla CSS!
Also, to cover and give your thoughts on Refacting UI.
Just discovered Tailwind CSS I gotta say it's pretty slick as a design system. Took me a while to wrap my head around TW CSS and frameworks in general. I think theres a severe lack of videos covering the basic concepts of how these frameworks... work and how to use them explained in simple basic terms. For someone new to them it's really confusing.
Also, a good video would be on how to make your own framework based around your own personal style.
Always look forward to your new videos!
I hope you have videos concerning all these properties cause I have never heard of most of these.
12:19 Subgrid, :has and container queries are the main features I would like to use, but I don't because the browsers support is not ideal yet, It is good to see I'm not alone
It's such a shame that Digital Ocean have effectively killed CSS Tricks. 😥
Yeah :/. But at least there are still lots of useful articles we can read. I also often find them when I search for something. So the project is not really dead, it's just frozen, I would say.
since when is css tricks powered by digital ocean? what is now the future of this page?
@@groovebird812the announcement was from 15 March last year.
Buying a beloved property just to kill it off is one of the most evil things you can do. I will NEVER use or recommend Digital Ocean, EVER.
Could you please briefly explain what you mean, or point me to a source where I can read abou it?
On the topic of Tailwind, I am definitely in the it's not for me camp. I have tried it, I am even using it in a current project and I feel like tailwind cannot replace plain css, at least not completely. I constantly run into things that I want to do that I could do in css, but in tailwind is not possible or it would be too hard to read all the classes or people are just saying do it with javascript.
Amen.
it's for prototyping and teams needing to ship fast.
Beyond that it's a delusional ecosystem.
u know u could use tailwind and vanilla css together right?
First things first.
I'm doing the Odin Project, and watching your videos... thanks a lot.
I'm 56, no more time to lose.
Now, a point of view I would like to share.
It's a kind of easy to play guitar, but those who understand music theory have much more insights, or material for creativity, due to that.
I really will learn the root thing before easy my way with these tools, due to that.
Tools do not provide creative thinking, problem-solving thinking.
So well deserved that you are number 1 of the people we follow for CSS 🙌! I learned a LOT of modern and advanced CSS from your videos, and I just love how you present the content. Even for simple concepts you always provide additional background info - showing that you did a lot of research. I appreciate it very much that you share all this knowledge with us! 🤝
And on top of that, you are just such a nice guy ❤. You just proved it again by your humble reaction to the result of the survey. So many reasons that I don't miss a single of your videos. 🚀
Totally agree. Kevin is simply Awesome!!
I still use Sass a lot, not with every project, but quite a bit. I'm in the boat with you though when it comes to not using TailwindCSS, I'm just personally not a big fan of it.
tailwind is amazing. I always check the stack of sites I visited - more and more often I see tailwind used.
im working on a new css framework right now 😅 and the state of CSS survey has given me a ton to learn about on this journey. it's fantastic to see the CSS community bustling with ideas and modern approaches to web development. gives me a lot to do!
I know i'm about a year late in watching this but I think it's important to understand that UnoCSS is largely a drop in replacement for TailwindCSS (if you use the default settings) but goes a bit further in allowing you to create your own grammars/rules/etc. In a way -- though it's definitely an imperfect comparison -- it's like JS and TS being considered different languages when compared against other languages. It tries to distinguish these two flavors but in doing so reduces the overall dominance that JS/TS and Tailwind/Uno have in the space they occupy.
Open Props, baby! Yeah!
I didn't read through all of the above comments, but I love working with Tailwind as well as working with vanilla CSS and SASS. That being said it is important to know how to use CSS before reaching for Tailwind. I simply view Tailwind as an alternate way to apply CSS. Maybe the thing I like most about Tailwind is the configurable design system out of the box (and tree shaking).
I wished I knew about the survey, I feel like I also miss these kinds of things 😅 Subscribed for the newsletter now, maybe I'll be able to take part next year
I just want to say, I love using raw CSS instead Tailwind.
Picked up TW when I had the chance and midway through the project just switched back to vanilla CSS lol
+1
The GOAT stays in the top! Well deserved 👏
Congratulations Kevin!
CSS frameworks have come and gone over the almost 2 decades Ive been working with websites and I have dipped my toes (well, actually for a few instances deeper than that) but I always find myself relying more and going back to just pure CSS. Theres a certain amount of peace of mind that although frameworks trends rise and fall every day, you can always be sure to rest on the foundation of knowing how to create and edit clean and lean pure css.
I see the advantages of using Tailwind but i simply cannot make myself write such bloated html. I prefer to focus on writing minimalistic and efficient css.
Congrats Kevin!!!!! 💛💛💙❤
17:03 this seems like a bug in the survey. ":has" is shown as most adopted, but then text below talks about gap support for flexbox. It looks like only the comments award is shown properly.
You are the face of CSS
UnoCSS to rule them all!
@property is - according to caniuse - actually coming to Firefox in 119 as well (117 released late august for reference)
I am a fan who honestly, also wishes you also make tailwind content. I always re-implement the design ideas I learn from you into tailwind so I feel there is more similarities and that much divide.
And i mean that seriously, its to the point that i wish there was someone on the internet just as good as you at teaching and being entertaining in javascript instead of html and css. In fact please do let me know if there is anyone you know of that you think is great at teaching javascript whether it be in text or video form. (As you probably can tell i value your opinion very highly...)
Web Dev Simplified is pretty good imo, and an underrated channel is @DaveGrayTeachesCode
Thanks, I appreciate the response :)
Thank you for helping me fall in love with CSS
Congrats on being no #1 ! Also, Panda is used to convert sass,scss to css on early days before ruby scripts and VSCODE extension which in most cases deprecated by new tools
I'm really curious if there's any correlation between React and Tailwind usage. It always feels like people only like Tailwind because React doesn't really allow styled components unlike other frameworks.
Love this survey and U R awesome.
I hire/manage product teams, and I wouldn't bring in an external team without using tailwinds. It's ok to have custom css but for maintainability, bringing in new devs, and long term maintenance I think tailwind css is great.
love tailwind from the beginning. never leave the code anymore. easy to use. even for small projects.
He is number 1 and doesn't want to be called king.
Our humble king you got it we'll deserved 💛
I write my css in vue JS as an object with values of css
Great topic
out of curiosity which framework are you using? thank you
Tailwind. Hmmm... that's a contentious one, eh? I'm old school, and have always hand-written my own CSS (using OOCSS/SMACSS/BEM methodologies, etc), creating components/legos. I personally hate Tailwind. I had to use it in 1 project, and it killed me a little every day. But... I do understand why some people love it, especially if they're not so well versed in the nuances of CSS (i.e. cascade/inheritance/specificity).
Agreed 100%. That's the problem that CSS needs to fix, IMO. I've solved it with using SCSS modules (e.g. Component.module.scss), requiring me to name my CSS class exactly the same as my component. And, like Kevin, I simply select my nested HTML elements (semantics matter!) instead of coming up with more class names.
When CSS supports proper scoping (work in progress) I'm sure it'll take a turn for the better. For now, only web components can scope CSS to a single component using vanilla HTML/CSS. Unless you use pre-processors like SASS and (S)CSS modules.
I personally hate it too, I think it’s an abomination. IMHO it was designed for JavaScript nerds who don’t know how to design anything. That said I don’t use any frameworks unless I have to, I use my own custom tools built with Sass so idk. 🤷♂️
@@mahadevovnl I've recently used Astro on a couple of small projects, and I used a mix of "global" CSS/Sass partials for setting up custom properties / reset / typography / grid system, then locally scoped "inline" CSS inside the Astro components. It worked really well.
To be honest I kinda do like Tailwind and I do understand CSS nuances you mentioned and in the past I've used many CSS methodologies you mentioned in your comment. I think it's bad to generalize like this implying "Tailwind is used by developers that don't know CSS". You cannot really use Tailwind if you don't know how to use CSS.
As with everything else in programming, it's just a matter of tradeoffs. I wouldn't use Tailwind for a landing page or a simple website with few pages. On the other hand if I'm working on some modern component based application, then it's definitely a good candidate for a project.
@@rand0mtv660 The point with "You cannot really use Tailwind if you don't know how to use CSS." is that if you knew CSS, you would use CSS.
Those who default to TW don't know CSS (also in my experience interviewing many people) and they make a huge spaghettified mess of it.
TW is tech debt from day one, a complete vendor lock-in, and is full of anti-patterns.
My guess? Five years from now, as CSS keeps evolving, TW will be a thing nobody likes or wants to work with anymore (like Bootstrap has fallen out of fashion, which is much less opinionated and divisive) and, well, good luck finding people to help you maintain your monstrosity of an app with 10+ to 20+ or even 40+ of utility classes in every single HTML element in your ENTIRE app.
It's not future-proof.
Saying "TW is CSS" is just a way of saying: "I don't know what I'm talking about."
I'm seriously astonished at how many people like something this stupid :D
Great video! 🔥
@12:59 SVG-in-CSS. Anyone know what is meant by that? U can define svg backgrounds in css when encoded.
First of all great channel...The answer to the question is; most likely. But there is no greater mark on a design process and outcome then the creativity inspired by vanilla CSS. Although Tailwinds does leave room for some ingenuity, I find it's like working with another artists' brush. CSS is the art work, not the framework.
Hi I try to make personal projects and struggle with picking colors. What rule should I follow maybe make new video on this topic since you are the best thanks!
Thanks Kevin
I started css bc of u 😂, when u start tailwind I'm 1000% in Hhhh
Kevin, please guide me. I'm a newbie learning CSS. Should I expend any effort learning Tailwind. Please explain how this is going to help me.
I think you should have a solid understand of css before even considering tailwind css
@@vrildox-to7ir , please somebody explain why I should learn tailwind css.
Tailwind is just a tool that can help you work a bit faster, if you don't have a good understanding of CSS itself it won't really help at all
You have to know CSS to use tailwind. If you don’t understand css at all then tailwind isn’t going to work.
Hey Kevin, as a pro in CSS what do you use to make a Streamlit project look good? Pure CSS, Tailwind…?
I feel like Tailwind is new Bootstrap.
Mobile traffic surpassed the 50% of total traffic a couple of years ago, its crazy that drop off in testing.
I hope that they at least test in responsive mode (on their desktop device).
A video about anchor attribute ,please?
Have you thought about doing CSS news or JS news? That you scroll news. and talk about it?
Cant wait for the subgrid 😂
Congrats! Kevin on being Numero Uno 👏
Ive tried to get into Frameworks a lot, because it always felt like people who take webdesign seriously use css frameworks. But always out of like "obligation".
But honestly, after like 15 years, I'm gonna stand up and say it: Pure CSS is very writable, you don't need a framework to make your life easier here. Especially if you go for smart, minimalistic solutions. I'd say you even come out on top if you count all the setup and the compatibility issues created by switching other frameworks in your project. Pure CSS just works and you can slap open the dumbest text editor and fix a small problem in a minute instead of going through all the overhead created by the framework. The lot of them feel like taking your car out for a 200m drive to the supermarket instead of walking.
not online tailwind. windy css. unocss, is kind tailwind style
But Tailwind is basically CSS but inline (without the limitations of actual inline CSS)
Not really like those CSS framework (Tailwind, Bootstrap etc.)
What I think is..the time I spend on searching relevant classes to apply the style is too much, where I just need a couple of seconds to apply the style if I type the CSS out.
Beside, I just don't like the HTML DOM look so mess with so many classes..
I don't use tailwind css for large project
Tried tailwind. Hated it. Each to their own.
tailwind is fine, but it isn't a silver bullet. i still find writing stylesheets to be very enjoyable although using tailwind or similar tools for quick projects is still awesome.
For CSS in JS solutions they're all dropping significantly on new project because they require a runtime on the client side to work, and with the last version of React and server components all the styling is computed serverside (or you have to disable server components which has a high negative impact on perfs).
I love using it. It’s a pain using custom css.
Sir I am new frontend developer and I use simple css. I was thinking of learning tailwind.Can you help me in what css library i should learn to grow more
Hello folks, do you agree that many frameworks are chosen by the leaders, not by the programmers?
Yes, for sure. 😉
Wouldnt IDs, specificity and good commenting in the css file be more beneficial.
hello dear, can you tell me about your mic, mixer and camera?
*Ayo, chill. I just started learning CSS* 😭
If I learned a language it would be Tailwind or PurgeCSS. Because these aren't loss poularity like a Bootstrap (I think bootstrap populartiy loss 20% beetween 2019-2023.).
I wonder your opinion. suppose If you going to learn which one would you choice?
Thanks your answer Kevin.
I don't use Tailwind as well. Nothing against it, but nothing pulling me to use it without it being a work necessity. Which hasn't happened yet.
I use Tailwind and CSS together. I see them as having different use cases. Tailwind is for quick and dirty inline styling wheras css is for more detailed abstracted styling.
I never knew Tailwind was so popular, I thought it was a niche Laravel thing. I think it will have its moment in the sun and then fade away - like jQuery. jQuery used to be a must have skill then Node and Vue / Angular etc. came along and people started getting back into raw JavaScript again. CSS frameworks and libraries are the same. They will fall in and out of fashion but there will always be base CSS.
I only use Tailwind because its now part of the Laravel framework.
I never liked Bootstrap - I either call it 'Poopstrap' , 'Bloatstrap' or 'Blandstrap' in my head. I prefer Tailwind because its more flexible and doesnt force you to write confusing layouts with loads of nested elements.
As CSS is evolving at such a pace into such an awsome language I only regret not having enough time to faliarising myself with its new features more because those make learning new css frameworks and pre-compilers increasingly pointless.
short answer yes in 90 % of cases
I miss Pico.css within the frameworks
Watching...
Tailwind = inline styles with extra steps
Tailwind taking over CSS? NO; CSS becoming Tailwind? probably YES.
The reason tailwind usage slopes like that vs retention is because it's been shoehorned into so many projects that need to make a quick prototype to demo the core of the project.
Since the projects goal isn't CSS they reach for token based styles to make something quick forcing a lot of downstream consumers to be convinced they also HAVE to use it to build on top of the starter code.
Similar in effect as bootstrap leaking into everything in 2011+ but with much heavier network-effects pushing hype-awareness and forcing usage in the current web vs how frameworks propagated a decade ago when bootstrap came out.
Then retention kicks in as downstream consumers of those projects start hitting the problems caused by using something like tailwind when you aren't prototyping or a large distributed team.
But the retention doesn't nosedive because have you ever had to gut a token system out of a component project.
Web-development tooling is broken.
I think TailwindCSS vs. Bootstrap. You either use one or the other at your job and most likely hate the one you have to use due to the previous Devs thinking something about it that they should not have. Like they wrote "!important" to overwrite something they 100% did not need to.
For testing why test on things other than desktop/laptop, if you only have to support them (work-related internal applications). I would say still test on different widths which I see people do not and some of the sites look bad even at max 1920px.
In UX that !important issue is known as a Desire Path. These indicate flaws in the UX of a system. (The classic example is dead grass where people walk instead of walking on the designed path.) The underlying problem with all of these frameworks is that they trade off flexibility for usability. That works great when you're starting out or working together with people on a big project, but creates impedance for people that know the underlying technology. So, they find "creative" ways to work faster, creating unintended knock-on effects.
You can't _control_ human nature. You have to design around it. This is the lesson of Desire Paths. You can't just tell everyone not to walk on the dirt path everyone prefers. You can't moralize the issue away.
I do not disagree with you in general.
It seems to me it is a lot of a lack of understanding though. Meaning 9/10 times you can just remove the "!important" and nothing changes. Also in both Bootstrap and TailwindCSS, there are better ways to change most of the defaults in their controls just requires develing more than a minute into the library.
I tried creating a pet project with Tailwind to learn it and as I added more and more functionality tailwind in my Vue templates became unreadable. So good for quick, bad for big
Maybe I'm biased, but SR's aren't really that hard :')
...I mean, I'm also blind and have been blind for a long time. But still >//
Also browser compatability.
Back in the day
When you had to code shit specifically for IE :')
Honestly, give me 1 or 2 reasons why people would hate TW?
Don't waste your time to learning css deeply ....focus on programming language as much as you can....
that's why there are no programmers who is good in css.
6:23 +1 for not using tailwind
Scrollbar styling is far from being in a good state. Not only do we not have a consistent cross-browser solution, the solutions that do exist don't even work the same across platforms. Even after 15 years of working, this is something that can only be solved in JS...
With JS you mean hiding the native scrollbar and building a custom one with a custom component?
Would you write like this in JavaScript:
document.writeln("");
document.writeln("...");
document.writeln("");
No matter your level as a frontend developer, you will inevitably be disgusted by the above method of writing.Similarly, why is the concept of:
class="inline-block bg-gray-200 rounded-full px-3 py-1 text-sm font-semibold text-gray-700 mr-2"
Why is it revered? Both are essentially hardcoding in the wrong way. The concept is identical in both instances.
CSS can certainly be described with any tool, and no one would complain about that, but you should not describe CSS in the worst possible way.Then you tell me how excellent Tailwind is. If you think Tailwind is so great, then doesn't the practice of document.writeln(""); also become excellent?
Those who like Tailwind always like to criticize other CSS frameworks, which I think is just arguing for the sake of arguing, and it's meaningless.Tailwind claims high development efficiency, and admittedly, this is true, but it brings about management hurdles and a learning curve. The author of Tailwind provides corresponding solutions and tools, which, ironically, prove that what you develop yourself can cause many problems; otherwise, why would a simple CSS need so many tools for optimization?
Stop fooling yourself here, Tailwind is just a terrible product of the times.
Tailwind is good
Kevin, do you finally accept your title as King of CSS?
The people have spoken 😅
While tailwind rises, you still need to know CSS to use it consistently.
And people these days refuse to learn CSS
Tailwind: Naming things is hard, but it's impossible if you never practice using nouns.
TAILWIND HATE!
I don't want to live in a world where Tailwind has taken over, because I've been there, it's called the 1990s, when every style was inline and there was no separation of concern and no semantics in styling. It blows my mind that people are flocking back to this incredibly bad way of representing styles, but herd mentality is what it is.
Tailwind sheep telling you separation of concerns doesn't work in 3,2,1,...
Css is supreme to any other design pattern. Nothing is as flexible...
I think It is not Tailwind it is AI is taking over 😂😂
css trend is too fast to follow, especially working with team, so tailwind could be the answer
Tailwind's not for me; it's like tying my hands behind my back and working with my feet.