Tailwind CSS is amazing library. It really is. I want it to succeed. But I'm not using for all my projects anymore.
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
For some of the new projects I'm working on, for most of my new projects I'm working on now these days, I actually switched away from Tailwind. I'm not using Tailwind in those projects also not ShadCN, therefore. And there is a reason, and the reason is not that Tailwind is bad, of course. Quite the opposite. It's an amazing library, I wanna be very clear about that. And I kind of also feel bad about making this video, this episode here, because only a few weeks ago, I talked about the huge financial
problems Tailwind was facing back then. Now, since then, thankfully, things got way better, many new sponsors jumped onboard and now I think they're in a much better financially, because, of course, obviously, Tailwind is amazing and there are people working with a lot of heart and energy on that project. And my point is not that it's bad or I wanna convince anybody not to use it. I mean, I'm just using this channel to share my and some insights into how I work, so I thought that might be
interesting. So why am I not using Tailwind then amazing? Well, I gotta take a step back. A couple of years ago, before we had the AI revolution or before AI got that good at coding, I used Tailwind like most people, I guess, most developers everywhere. For one main reason, though. Because it allowed me to iterate quickly on the code. You know, I never really used Figma or other tools like that, also, of course, because I'm in the situation
working alone, and if I'm working alone on my projects, really have to use those design tools. For me, it always was quicker to iterate on designs just code. I could write code, and with Tailwind, since you have your classes inline in your DOM, in your JSX code, you could quickly update that code, update those styles and try out different styles, try tweaking that margin. And that was just a- a very, very efficient flow. And that was the main reason for me, and maybe also for some other developers,
I was using Tailwind. I know for a decent amount of other developers, maybe the majority, another strong reason is that they just hate CSS. I know CSS is not popular amongst web developers and I get why. It can seem very complex, there are hundreds and thousands of properties and values and, yeah, it- it can be daunting. Now, I will say, though, modern CSS has come a long way. Many things are easier now than they were in the past. I mean, Flexbox is not new at
all anymore, but it made a lot of things easier. And now think of Flexbox in other areas where deriving colors got way easier than it used to be. You have relative colors now in CSS. And by the way, on my Academy channel I launched a couple about modern browser and CSS features, like colors and relative colors or the container queries, which are also amazing for building dynamically, uh, resizable components that don't depend on the viewport but on the space that's
available to the component. So CSS has come a long way. Now, the thing is, you can use all these modern CSS features also with Tailwind essentially, or most of them, but you can also write vanilla CSS and you can do that even easier now with AI, of course, because even if you hate using CSS, knowing about certain features and their browser support can be enough You can point AI at the features you want it to use, at some docs, some MDN articles that explain those features, and
AI can write the code for you. You might wonder why you would do that, why not just use Tailwind? I mean, it has all these modern features too. For one and a half reasons, I would say, at least for me. The less important reason is that Tailwind might not always support all of the latest features, and more importantly, AI certainly doesn't know about all Tailwind features. I mean, Tailwind ha- but AI doesn't use all of them. It always uses the same
few classes, and often even an old class syntax, so you're missing out on certain features here. Now, the same can happen for you if you are using vanilla CSS, of course. If you don't tell the AI to use a certain feature, it just might not. But you can learn about the few most important CSS features you wanna use and then tell AI to do so, but of course, point, you could also do the same for Tailwind use certain Tailwind features. Uh, it just might be easier to just name a couple of key CSS features than Tailwind
classes, but again, that's not my main point. My main point is that I have always tried to reduce the- the amount of libraries I use in my and the- the reason for that is twofold. For one, I create educational content, so I'm used to, uh, external or extra libraries being a bad thing, because if I create a course about React, use Tailwind, if there is a breaking change in Tailwind, a lot of parts of my code, uh, or of my course suddenly start breaking
get a lot of questions by students, even though the main topic, React, have changed I get that this is a very niche problem that affects me, but not most web- websites though. But even if you're building a normal website, having as little third party libraries in there as poss- uh, possible and reasonable is a good idea, I would argue. Now, I will also say that it's not a good idea to absolutely force every library out there. There is a good reason to use
certain libraries. I mean, if you're using, uh, a rich text editor, using something like TipTap makes a lot of say, because you can build your own editor. Now with AI it's easier than ever to some degreeBut you will also run into a lot of edge cases or problems you then have to solve yourself, with AI sure, but also AI doesn't get everything right. You know that if you worked with it. So there are reasons to use third party libraries. I'd just say that styling, as I explained, is something that is
actually replaceable. Again, not saying that everybody should be doing it, but for me that works quite well and therefore library that I can get rid of because I don't mind reviewing the CSS code, uh, AI gives me and fixing CSS and styling problems with raw CSS when things go wrong because, of course, things will go wrong (laughs) at some using AI. But I don't mind that. If you absolutely hate looking at CSS code, that will not be an option for you,
But for me, I therefore can get rid of the Tailwind I can get rid of ShadCN for example, because I built my own components and ShadCN of course is not a traditional library but it does use Radix UI under the hood, a library which has a questionable maintenance status, uh, now as far as I know. So there you then have the actual problem why I wanna white libraries even when not talking about educational content, if it makes sense.
Every library you add to your project can also become a liability if it stops being maintained. At that point, security issues might not get fixed anymore. Bugs might not get fixed anymore. Styling bugs, for example, with Tailwind. New features might not be added anymore. If there is a new CSS feature and Tailwind weren't maintained anymore, course it is, but if it weren't maintained anymore, use that feature. And, I mean, we kind of were close with
Tailwind. That video which I created where I talked about their problems, there is a post by the main Tailwind says if they can't figure out this financing problem, Tailwind might become abandonware. Maybe that was a bit drastic, maybe also done to get more attention, but nonetheless one problem you always have with most third party libraries is that they might not be maintained anymore future, depending on who's working on them in the And that's why I personally like using vanilla CSS again.
Also, and that's important here because I always so, and again I can't emphasize it enough, I want all the best for Tailwind and I'm still using it in, in many projects. It's not like that. I don't hate it. It's just one thing where I'm experimenting with not using it in some projects and no matter if that's Tailwind for you different, I just would... And, and that was true before the AI era too. I would always consider twice before using party library. There are many good reasons to use them.
For example, BetterAuth for authentication is amazing. I would definitely do that. But if there is a library you can replace, it might be worth a second look or thought, I guess
GPT 6 Astra was released. It's a good model, I have to say. Especially for 3D work it seems to be a real game changer. But due to all the hype, you may be disappointed...