Unpopular opinion Kyle works for google in speach recognition depratment

I was literally just searching vue-tailwind when I got the notification

Maybe you both get the same recommendations

Ikr! He made this video right when I was thinking about using Tailwind

Same . I just got a job and they want me to learn tw

Where did u learn react ?

@@rayanall7333 by building projects you don’t need to learn react you need to understand the vanilla javascript and es6 then you’re ready to go with the documentation of react.

Can you share?

LMFAO 🤣🤣🤣

Kyle's was like:- concentrate on content not my Hair, lol😂

Damn. I was gonna say he truly got hit by the Tailwind.

impossible

As for React, i pick ChakraUI in place of Tailwind

@@abdulazeezolanrewaju843 oh yeah I built my blog with that. It's sweet! But even that is a layer above tailwind. If I'm not mistaken.

@@abdulazeezolanrewaju843 is ChakraUI more powerful than Tailwind for React?

@@husler7424 For me Yes, in the React World. you can also give it a try :)

@@ZubairAhmed1024 Yep!!

Check out The Net Ninja's Tailwind playlist. It's a great jumping on point.

ye

Bootstrap doesnt have css purging OR tree-shaking. And most tool that does it usually doesnt play well with bootstrap

Here's hoping no one besides you ever needs to work on it.

How big is your 2 projects?

(tech stack- next.js, tailwind, react-query, prisma, postgres)

@@sreekumarmenon I mean how long these two took to complete, and how big the amount of users the app serves

@@genteka5106 I had posted this info, looks like youtube deleted it because i had linked to the app. it is a medium sized project that took couple of months . not sure how the number of users impact the choice of CSS framework.

Actually Tailwind CSS have jit and can be easily added to already existing projects. You can quickly find guides for that.

@@eugenereim456 But when it's just CSS properties as classes, what's the point?

@@Kayzewolf Design system components

@@Kayzewolf built in media queries, enforcing consistency in layout and spacing, and less actual code to write. You can see examples on their website where in raw css it would be 20 lines, whereas in tailwind its 4 lins of html and a few classes.

@@Kayzewolf you dont want to search for 50 css file to find out exactly what is applied to the one random div

But why write that in a style sheet when you can just use regular styling. I think margin-inline: 50px is way more readable and does the same thing.

​@@ronaldtorres3366 But what benefit does a long line of @apply statements have over regular CSS? Especially when using the [] syntax as it's not even consuming any design tokens. It's just using Tailwind for the sake of using Tailwind, which isn't a great way to work. IMO, it ends up creating a codebase with a higher technical debt and with really gross git history. All of the git diff in commits will be on a single line, as apposed to having 1 CSS rule per line and seeing the commit changes much easier.

Lol loops inside CSS thanks

@@eotikurac not really

I have a huge project made with scss, and it's totally a pain. sometimes a class is used in multiple components and if you delete one component you are not sure if you need to delete the scss because you might delete something important that will completely destroy other components, pretty difficult tho.

tailwindcss sucks! pure bullshit and dirty code. Imagine the situation when you see lines and lines of crap mixed with logic when working with tsx or jsx. besides having to put classes to everything. To this day nothing is better or faster to write than scss.

​@@mmadictos5356 tailwind is soo clear

Tailwind comes with integrated postcss plugin that allows you remove all unused classes and your css file can be less than 50kb

​@@eugenereim456 there have been ways to do that way before tailwind. Using tailwind adds more CSS than it removes because you can't shorthand tailwind. (try margin:0 auto)

I'm always amazed that there are stratum of people who have such a limited imagination that they can't come up with random arbitrary names.

@@Maleficarum999 Seriously. Worst case scenario, just call it wrapper. Need two? Outer and inner wrapper. But honestly anyone who struggles with thinking of appropriate abstractions is probably not very good at software design. That's what software design IS.

Kinda in the same boat. I prefer doing it the traditional way since I could use the practice anyway.

feel jelous by the people who use tailwind

Which is why i like svelte, its all in one file; html, js and css :D

I agree 👍

@@aaronrothwell7615 I'm react developer and sevelt looks so wired to me lol 😂

@@aaronrothwell7615 Fellow svelter! Svelte + Tailwindcss is such a powerhouse it should be industry standard at this point. Although.. with svelte, what with css being scoped to a siongle page and all, the problems of native css itself is mitigated, so much so that I actually could do away with Tailwind in some occasions. I don't know. Maybe it's just Svelte that's the real MVP here.

Yeah you can use that with Tailwind installed as a npm module with @apply -classes.

Yes but by that time I've already called a predefined Bootstrap class and it's done.

@@ToddDunning ...which looks like shit. That's fine in some cases though, but if you're making a public website you don't want it to look like every other bootstrap site.

@@precumfrank7597 you do realize that you can change all the value over the Sass file right? If you don't want/like the default theme of BS, you can customize it without having to re-writing the whole framework.

That would be cool! There are some good details at tailwindcss.com/docs/font-family#font-families on replacing the 3 default font family values sans, serif, and mono with your own or defining new family names like display / body.

Agreed, utility class frameworks are trash

@@___jd Ok sir

I think tailwind can be useful when you're using something like React, where emphasis is on reusability of components. I wouldn't really see myself using it with vanilla JS though since it can get messy. EDIT: I realized that he talked about what I wrote towards the end. I should've finished watching the video before commenting...

@@giorgiotran4850 yes, I agree with that and I understand but still, remember that there are other ways to scope components style (i.e. Vue' scoped style). However, I didn't want to criticize Tailwind, it was a sincere doubt.

I have worked with and without tailwind for a some time, and oh man is it useful. If you know what you are doing, tailwind gives the ability to instantly know the structure and style of a component just by looking at it (the class naming is done great). It gives you an easy file (tailwind.config.js) to theme your whole web app. And gives you the ability to really customize your styling, "unlike bootstrap" with custom values. Going with the flexibility of having both (HTML, CSS) in one file (or component) makes your life easier. Instead of switching files between HTML and CSS or scrolling up and down the document like with (styled components), tailwind lets you focus on the element itself and once you get to know the framework, makes iteration incredibly fast. I recommend tailwind to almost anyone in frontend web dev, since I haven't seen any downsides to using it. Saying it looks messy is just not having the understanding to read what the classes are doing.

Thanks for letting us know!

Then what's the point of using apply directive in CSS file when you can write css directly in CSS file.

@@FaizanAnwerAli then you did not really understand what Tailwind CSS is about. It’s not only writing utilities inside the html but it’s all about productivity and time saving by simplifying your life with CSS. I don’t remember be able to deal with responsiveness so easily that tailwind does with a simply md:class rather than writing classic CSS. Grid management is also another subject where tailwind will help you earn some time

@@flo_dev last month I wasted more time with tailwind than I actually do without it. It's useless

@@FaizanAnwerAli 😅

shopify uses jquery for themes? I understand that its uses Remix ( react ) now.

if you look into it, it offers more, specifically its a design system which you define. Plus, its not inline styles, theyre actual CSS class declerations.

consistency, says you have new members in the team, if they already know Tailwindcss classes, it will be easier for them to get started

because Tailwindcss offers the same toolset for all users, easier for every one to understand what classes others are using mean without having to surf through the css files

@@Forien it's a lil faster

a dev mostly start avoiding design or architechture fatigue and also decision fatigue, for me vanilla css creates the former one, suppose you've two divs which share some common styling like border or flex, in css you get a choice to just include the common styling once, and that's where the design fatigue comes, now ive to look at the whole fking code to try to optimize the best minimal css which is fking pain, in tailwind you use flex property in both the divs seperately, more work but more clarity, also when you start styling a div, it gives you more perspective about the children elements and you basically starts imagining better how the site will look, you get better at css altogether

learn css so you will be able to do that, kekw

Tailwind pretty ez to learn also there's tailwind config where you can literally define css rules. For example you can set h1 to have certain classes engraved in it so you don't have to write everything. Literally righting just (no classes) will load your defined rules. Also tailwind can be used with native css which means they have same flexibility level vs bootstrap. Also hover states focus and element states. Really simple in tailwind.

@@nikyabodigital You don't need tailwind to write css rules to tags. My point is that whoever made this video, never actually used bootstrap.

@@JackyPup People today are getting mad with consolidated tools that have more than 2 yrs old, and all I see are buggy apps everywhere 😂

You don't know CSS

The docs are very good and they also have a good channel here: kzfaq.info/love/Oe-8z68tgw9ioqVvYM4ddQ

No need for tutorials actually. If you know CSS, you can easily grasp Tailwind in a day.

Anyone that understands CSS will grasp Tailwind in 5 minutes... and then not use it :)

You can specify (and you should) your design system colors like "primary-button-color" or "main-color" and so on.

Couldn't agree more. Just ended a Node.js Express Mongo course, my first year at studying programming, all with JS. I can't imagine using a CSS framework that just turns css properties or a mix of them into predefined classes. Makes no sense for me, just master CSS and learn how to reuse classes or combine them and that's it.

"new" is tragically seen as better unfortunately...

Part of being a developer these days is frustratingly forgetting about the stuff ingrained that you weren't suppose to, that you are encouraged to do now smh.

It’s not the first time the IT industry was wrong about something for 20 years before learning from failures. I only say waterfall model and itanium (very long instruction sets architecture) and mainframes

Its very similar but a lot easier to use

Soto easier to work with and alot harder to look at 😂

Comeon bro it must not be that hard . I know tailwind code looks massive sometimes but not that bad . Maybe I didn't work at any company before and don't know what do u mean by that Can u explain what was the hard part about tailwind ?

you could say the same with pure css

That sounds like a problem in your code not due to tailwind

in your component, you should place a prop that can modify the styling, if you are using React

it's shorter and faster to do? Don't know honestly, I'm quite new

The one advantage is, that you are able to easily change _everything_ with a certain property (like a 10px margin) in one go. Imagine, your designer tells you, that all 10px-margins should now be 12px. Or you want to create a responsive layout, where (controlled via media queries) for a certain screen size all 10px-margins should be 7px. Tailwind (and similar) adds another layer of abstraction and allows you to think about the exact design later after building the structure of your website by adjusting the actual values of the tailwind classes. But of course there are other ways to get the same result. You can use something like sass that offers various ways to accomplish the same (variables, mixins), or plain css variables. Also there are downsides of using generic css-classes. Of course your HTML becomes more complex and less readable. Having 10 classes in each element instead of maybe 1-2 bloats your HTML. Otoh you immediately get an idea what an element might look like just from looking at the list of classes it uses. In the end, tailwind (or the general idea of using generic css-classes) has advantages and disadvantages, like basically everything. It depends on the actual use case. If you want build a website with a very specific design, it might make more sense to write your own specialized set of classes, and/or use something like sass to combine those classes into the classes you will actually use in your elements. If you want just a quick site where the exact look does not matter so much, you can use bootstrap. If you want a more generic approach, or the classes bootstrap provides are not sufficient enough (because bootstrap doesn't have all the elements you need) tailwind might be the perfect solution.

@@imagiro1 Thanks for taking the time to explain the above. It's made everything a lot clearer!