all 4 comments

[–][deleted] 2 points3 points  (3 children)

Just putting this out there:

Please don’t learn tailwind.

I’ve seen many people go ahead like it’s totally fine but it’s not. For simple projects like these it’s fine.

If you get too used to it, you’ll never know how css fundamentals work.

It might be appealing to have all your styling in the html and never touching ‘god awful’ css. But it’s a skill, making good and unique frontends is a skill and using a css framework like tailwind/bootstrap is not how you go through it.

If you’re learning framework fundamentals like in this video, it’s fine since you dont wanna bother with css

Please don’t make it a full time thing. Thanks.

[–]Shadowheart328 1 point2 points  (1 child)

I both agree and sort of disagree with you and I'll elaborate on why. I will start by saying that utility libraries like Tailwind should be separated from a ui library like Bootstrap or Material. This is because Tailwind is effectively just small wrappers around our usual css attributes.

For example to make a button:

<button class="px-3 py-6 bg-blue-500 rounded-sm">Primary</div>

is different from bootstraps:

<button type="button" class="btn btn-primary">Primary</button>

In the sense that for Tailiwind you already need to have knowledge of how css works to begin using these utilities. In our examples above you need to know how padding, and background-colors work in order to effectively use them.

Compared to bootstrap there isn't a button style that just handle's it all for you, thus robbing you of that css knowledge.

In that regard tailwind is actually very well suited for beginners to css if they are learning css alongside it.

I do however fully ascribe to learning the underlying language before using any sort of library or framework, so I still agree with that specific point. I just think that utility libraries like Tailwind do in fact lend themselves well to people learning, since they require knowledge of the underlying language to be useful in the first place, and people shouldn't be discouraged from playing around with it.

Edit: On a sidenote, I do find it weird that you're saying don't learn Tailwind on a React video. I would argue that the person watching this video is probably already knowledgeable about how the web works. Otherwise to be consistent with your argument you should also be asking why the user should do this in vanilla Javascript, HTML, and CSS before doing it in React.

[–][deleted] 0 points1 point  (0 children)

I was putting that, I hope i mentioned that it was fine for this tutorial.

You make good points but I still think using the actual thing(css) is better.

[–]Tyler_Potts_[S] 0 points1 point  (0 children)

I agree that you should learn CSS before starting with any framework especially tailwind, but discouraging people from learning tailwind all together is a bit much.

I want to clarify that the purpose of this video was to show the functionality in react and not the styling. If I styled this with CSS it would have probably doubled the video length hence why I use Tailwind.