WEBVTT

00:00:00.100 --> 00:00:04.059
For some of the new projects I'm working
on, for most of my new projects

00:00:04.120 --> 00:00:08.000
I'm working on now these days,
I actually switched away

00:00:08.060 --> 00:00:11.940
from Tailwind.
I'm not using Tailwind in those projects

00:00:12.000 --> 00:00:15.820
also not ShadCN, therefore. And there
is a reason, and the reason

00:00:15.860 --> 00:00:19.790
is not that Tailwind is bad, of course.
Quite the opposite.

00:00:19.840 --> 00:00:22.600
It's an amazing library,
I wanna be very clear about that.

00:00:22.620 --> 00:00:26.440
And I kind of also feel bad about making
this video, this episode here,

00:00:26.460 --> 00:00:30.420
because only a few weeks ago,
I talked about the huge financial

00:00:30.430 --> 00:00:33.020
problems Tailwind was facing back then.

00:00:33.060 --> 00:00:36.480
Now, since then, thankfully,
things got way better, many new

00:00:36.580 --> 00:00:40.220
sponsors jumped onboard
and now I think they're in a much better

00:00:40.280 --> 00:00:43.500
financially, because, of course,
obviously, Tailwind is amazing

00:00:43.560 --> 00:00:47.150
and there are people working with a lot of
heart and

00:00:47.200 --> 00:00:51.160
energy on that project. And my point
is not that it's bad or

00:00:51.260 --> 00:00:54.330
I wanna convince anybody not to use it.

00:00:54.330 --> 00:00:58.060
I mean,
I'm just using this channel to share my

00:00:58.100 --> 00:01:01.220
and some insights into how I work,
so I thought that might be

00:01:01.280 --> 00:01:04.709
interesting.
So why am I not using Tailwind then

00:01:04.760 --> 00:01:08.520
amazing? Well, I gotta take a step back.

00:01:08.600 --> 00:01:12.160
A couple of years ago,
before we had the AI

00:01:12.220 --> 00:01:15.400
revolution or before AI got that good at

00:01:15.440 --> 00:01:19.280
coding, I used Tailwind like most people,
I guess, most

00:01:19.320 --> 00:01:22.090
developers everywhere.
For one main reason, though.

00:01:22.120 --> 00:01:25.400
Because it allowed me to iterate quickly
on the

00:01:25.460 --> 00:01:29.420
code. You know,
I never really used Figma or other

00:01:29.460 --> 00:01:33.190
tools like that, also, of course,
because I'm in the situation

00:01:33.260 --> 00:01:37.240
working alone, and
if I'm working alone on my projects,

00:01:37.260 --> 00:01:39.760
really have to use those design tools.

00:01:39.770 --> 00:01:43.700
For me, it always
was quicker to iterate on designs just

00:01:43.740 --> 00:01:47.259
code. I could write code,
and with Tailwind, since you have your

00:01:47.320 --> 00:01:51.200
classes inline in your DOM,
in your JSX code, you could quickly

00:01:51.210 --> 00:01:54.960
update that code, update those styles
and try

00:01:55.040 --> 00:01:58.610
out different styles, try tweaking
that margin.

00:01:58.620 --> 00:02:02.110
And that was just a- a very,
very efficient flow.

00:02:02.140 --> 00:02:05.520
And that was the main reason for me,
and maybe also for some other developers,

00:02:05.700 --> 00:02:09.560
I was using Tailwind. I know for a decent

00:02:09.600 --> 00:02:13.480
amount of other developers,
maybe the majority, another strong reason

00:02:13.520 --> 00:02:17.410
is that they just hate CSS. I know CSS
is not popular

00:02:17.460 --> 00:02:19.609
amongst web developers and I get why.

00:02:19.720 --> 00:02:23.150
It can seem very complex, there
are hundreds and

00:02:23.280 --> 00:02:26.980
thousands of properties and values and,
yeah, it- it

00:02:27.080 --> 00:02:30.700
can be daunting. Now, I will say, though,
modern

00:02:30.800 --> 00:02:34.440
CSS has come a long way. Many things
are easier now

00:02:34.600 --> 00:02:38.340
than they were in the past. I mean,
Flexbox is not new at

00:02:38.440 --> 00:02:41.220
all anymore,
but it made a lot of things easier.

00:02:41.230 --> 00:02:45.130
And now think of Flexbox in other areas
where

00:02:45.140 --> 00:02:48.650
deriving colors got way easier than it
used to be.

00:02:48.660 --> 00:02:50.840
You have relative colors now in CSS.

00:02:50.850 --> 00:02:54.480
And by the way,
on my Academy channel I launched a couple

00:02:54.560 --> 00:02:58.049
about modern browser and CSS features,
like colors and relative

00:02:58.080 --> 00:03:01.760
colors or the container queries, which
are also amazing for

00:03:01.780 --> 00:03:05.190
building dynamically, uh, resizable

00:03:05.200 --> 00:03:08.989
components that don't depend on the
viewport but on the space that's

00:03:09.020 --> 00:03:12.280
available to the component.
So CSS has come a long way.

00:03:12.320 --> 00:03:16.269
Now, the thing is,
you can use all these modern CSS features

00:03:16.360 --> 00:03:19.710
also with Tailwind essentially,
or most of them, but

00:03:20.720 --> 00:03:24.240
you can also write vanilla CSS
and you can do that even

00:03:24.340 --> 00:03:27.940
easier now with AI, of course,
because even if you hate using

00:03:27.980 --> 00:03:31.920
CSS, knowing about certain features
and their browser

00:03:32.000 --> 00:03:35.900
support can be enough You can point AI at
the features you want it to use,

00:03:35.920 --> 00:03:39.680
at some docs, some MDN articles
that explain those features, and

00:03:39.720 --> 00:03:43.560
AI can write the code for you.
You might wonder why you would do that,

00:03:43.660 --> 00:03:47.280
why not just use Tailwind? I mean,
it has all these modern features

00:03:47.320 --> 00:03:51.140
too. For one and a half reasons,
I would say, at least for

00:03:51.180 --> 00:03:54.900
me. The less important reason is that

00:03:54.960 --> 00:03:58.640
Tailwind might not always support all of
the latest features,

00:03:58.740 --> 00:04:02.540
and more importantly,
AI certainly doesn't know about

00:04:02.560 --> 00:04:06.140
all Tailwind features. I mean,
Tailwind ha-

00:04:06.880 --> 00:04:10.720
but AI doesn't use all of them.
It always uses the same

00:04:10.980 --> 00:04:14.720
few classes,
and often even an old class syntax,

00:04:15.060 --> 00:04:16.720
so you're missing out on certain features
here.

00:04:16.740 --> 00:04:20.620
Now, the same can happen for you
if you are using vanilla CSS, of course.

00:04:20.660 --> 00:04:24.360
If you don't tell the AI to use a certain
feature, it just might not.

00:04:24.400 --> 00:04:28.180
But you can learn about the few most
important CSS

00:04:28.240 --> 00:04:31.920
features you wanna use
and then tell AI to do so, but of course,

00:04:31.960 --> 00:04:35.760
point,
you could also do the same for Tailwind

00:04:35.800 --> 00:04:39.780
use certain Tailwind features. Uh,
it just might be easier to just name

00:04:39.820 --> 00:04:43.140
a couple of key CSS features than Tailwind

00:04:43.280 --> 00:04:46.860
classes, but again,
that's not my main point.

00:04:46.920 --> 00:04:50.380
My main point is
that I have always tried to

00:04:50.500 --> 00:04:54.020
reduce the-
the amount of libraries I use in my

00:04:54.860 --> 00:04:57.600
and the- the reason for that is twofold.

00:04:57.640 --> 00:05:00.940
For one, I create educational content,
so I'm used

00:05:00.950 --> 00:05:04.720
to, uh,
external or extra libraries being a

00:05:04.740 --> 00:05:08.660
bad thing, because
if I create a course about React,

00:05:08.740 --> 00:05:12.680
use Tailwind, if there
is a breaking change in Tailwind, a lot

00:05:12.720 --> 00:05:16.690
of parts of my code, uh,
or of my course suddenly start breaking

00:05:16.700 --> 00:05:20.520
get a lot of questions by students,
even though the main topic, React,

00:05:20.540 --> 00:05:24.310
have changed I get that this
is a very niche problem that

00:05:24.340 --> 00:05:27.740
affects me, but not most web-
websites though.

00:05:27.760 --> 00:05:31.620
But even if you're building a normal
website, having

00:05:31.720 --> 00:05:35.320
as little third party libraries in there
as

00:05:35.380 --> 00:05:39.120
poss- uh, possible and reasonable
is a good idea, I would argue.

00:05:39.160 --> 00:05:43.130
Now, I will also say
that it's not a good idea to absolutely

00:05:43.160 --> 00:05:47.020
force every library out there. There
is a good reason to use

00:05:47.040 --> 00:05:50.930
certain libraries. I mean,
if you're using, uh,

00:05:50.930 --> 00:05:54.840
a rich text editor,
using something like TipTap makes a lot of

00:05:54.880 --> 00:05:57.040
say,
because you can build your own editor.

00:05:57.180 --> 00:06:00.996
Now with AI it's easier than ever to some
degreeBut you

00:06:01.006 --> 00:06:04.716
will also run into a lot of edge cases
or problems you then have to

00:06:04.776 --> 00:06:08.395
solve yourself, with AI sure,
but also AI doesn't get everything

00:06:08.436 --> 00:06:10.135
right. You know that
if you worked with it.

00:06:10.176 --> 00:06:14.015
So there are reasons to use third party
libraries.

00:06:14.116 --> 00:06:17.786
I'd just say that styling, as I explained,
is something that is

00:06:17.876 --> 00:06:21.676
actually replaceable. Again,
not saying that everybody should be

00:06:21.716 --> 00:06:24.916
doing it, but for me
that works quite well and therefore

00:06:24.955 --> 00:06:28.726
library that I can get rid of because I

00:06:28.736 --> 00:06:32.015
don't mind reviewing the CSS code,

00:06:32.135 --> 00:06:35.695
uh, AI gives me and fixing

00:06:35.756 --> 00:06:39.676
CSS and styling problems with raw CSS
when things go wrong

00:06:39.716 --> 00:06:43.586
because, of course,
things will go wrong (laughs) at some

00:06:43.635 --> 00:06:47.556
using AI. But I don't mind that.
If you absolutely hate

00:06:47.616 --> 00:06:51.385
looking at CSS code,
that will not be an option for you,

00:06:51.395 --> 00:06:55.226
But for me,
I therefore can get rid of the Tailwind

00:06:55.455 --> 00:06:59.336
I can get rid of ShadCN for example,
because I built my own components

00:06:59.376 --> 00:07:03.296
and ShadCN of course
is not a traditional library but it does

00:07:03.376 --> 00:07:07.145
use Radix UI under the hood,
a library which has

00:07:07.216 --> 00:07:11.176
a questionable maintenance status, uh,
now as

00:07:11.216 --> 00:07:14.876
far as I know.
So there you then have the actual

00:07:14.916 --> 00:07:18.596
problem why I wanna white libraries even
when not talking

00:07:18.655 --> 00:07:21.416
about educational content,
if it makes sense.

00:07:21.476 --> 00:07:25.155
Every library you add to your project can
also become a

00:07:25.195 --> 00:07:28.456
liability if it stops being maintained.

00:07:28.556 --> 00:07:31.996
At that point,
security issues might not get fixed

00:07:32.015 --> 00:07:34.836
anymore. Bugs might not get fixed anymore.

00:07:34.916 --> 00:07:37.676
Styling bugs, for example, with Tailwind.

00:07:37.756 --> 00:07:39.876
New features might not be added anymore.

00:07:39.916 --> 00:07:43.836
If there is a new CSS feature
and Tailwind weren't maintained anymore,

00:07:43.895 --> 00:07:47.596
course it is,
but if it weren't maintained anymore,

00:07:47.655 --> 00:07:51.476
use that feature. And, I mean,
we kind of were close with

00:07:51.556 --> 00:07:55.236
Tailwind. That video
which I created where I talked about their

00:07:55.296 --> 00:07:59.056
problems,
there is a post by the main Tailwind

00:07:59.155 --> 00:08:03.135
says if they can't figure out this
financing problem, Tailwind

00:08:03.195 --> 00:08:06.916
might become abandonware. Maybe that
was a bit drastic,

00:08:06.976 --> 00:08:10.676
maybe also done to get more attention, but

00:08:10.716 --> 00:08:14.416
nonetheless one problem you always have
with most third

00:08:14.535 --> 00:08:18.496
party libraries is
that they might not be maintained anymore

00:08:18.535 --> 00:08:21.395
future,
depending on who's working on them in the

00:08:21.416 --> 00:08:25.056
And that's why I personally like using
vanilla CSS again.

00:08:25.176 --> 00:08:28.456
Also,
and that's important here because I always

00:08:28.496 --> 00:08:31.945
so, and again I can't emphasize it enough,

00:08:32.116 --> 00:08:35.765
I want all the best for Tailwind
and I'm still using it

00:08:35.816 --> 00:08:39.466
in, in many projects. It's not like that.
I don't hate it.

00:08:39.496 --> 00:08:43.275
It's just one thing where I'm
experimenting with not using it in some

00:08:43.316 --> 00:08:46.456
projects and no matter
if that's Tailwind for you

00:08:46.496 --> 00:08:50.276
different, I just would... And, and
that was true before the

00:08:50.336 --> 00:08:54.086
AI era too.
I would always consider twice before using

00:08:54.195 --> 00:08:56.706
party library. There
are many good reasons to use them.

00:08:56.716 --> 00:08:59.695
For example,
BetterAuth for authentication is amazing.

00:08:59.796 --> 00:09:03.616
I would definitely do that. But
if there is a library you can

00:09:03.675 --> 00:09:07.356
replace,
it might be worth a second look or

00:09:07.536 --> 00:09:08.795
thought, I guess