Let's be honest. Writing CSS can sometimes be a b*tch. As projects grow larger, the CSS styles can become quite hard to maintain - from naming thin...
For further actions, you may consider blocking this person and/or reporting abuse
Long ago I've decided that CSS frameworks arent for me, and the main reasons for that are:
The third point is not a problem with purgecss that strip unused CSS.
But there is the problem of adding more tools to your tools. More setup, more reading docs, more breaking points with version changes etc
Si I suppose that you don't use autoprefixer for the same reason. Sure vanilla CSS is great but have a good time remembering all vendor specific prefixes. This will also reduce your CSS readability a lot...
It depends on the target browsers and project size, so no not always. For modern browsers it does little and vendor prefixes are being phased out of modern specs like grid. I’m not against tools. But there is a cost to each tool you add to a project. Adding blindly will bite you later
I've never understood how these tools are supposed to work. Even if you brute-force it by scraping the entire site you're going to miss a lot of dynamic classes added by ajax or rich text editors and such.
I can relate to these points. I agree with the original post that CSS can be hard to manage and organize as a project grows. However, as a UI designer, I like to design what I want to make before I make it. Once I am done, I always struggle to stick to my original design when using a CSS framework. Using CSS frameworks in my opinion is nice when I don't have a design in mind and I just want to cram together whatever I can find, but when I am following a design, I am trying to get the finer details accurate. When I am trying to get the details right, it's just a headache for me to figure out how to do that with the CSS framework I am using. As you said, it's more like learning the logic of a framework, and it becomes an obstacle.
I fully understand what you are saying about the usefulness of a framework when you don't have a design in mind or when you are prototyping. That's a scenario where I might consider using some framework too, as long as it didn't have a steep learning curve.
With my original post, I didn't mean to say that frameworks are inherently bad, but that they simply don't meet my personal requirements. Writing vanilla CSS has a few challenges of its own, but to me dedicating some time for it is worth it, as it is a knowledge that stays. On the other hand, if you dedicate time learning a framework and then move to the next framework, the hours that you spend learning the old one seem like wasted time, as they are of no use anymore.
Some time ago I had written a post of my own explaining those views of mine in more detail, for anyone interested.
Valid points, thanks for sharing them. I can certainly understand why you would rather omit the usage of a framework. However, as of now I'm still enjoying the process of experimenting with it but I am curious to see how my opinions & views will change in the future.
Your 5th point was actually the opposite for me. I hated css and never really grasped it fully. But css frameworks (tailwind in this case) taught me the logic behind css without all that bloated codes. And that at the end helped me learn css. I agree with all the other points you've made, but I would suggest tailwind to everyone just because of this one reason that it may help them understand the logic behind css easier.
I came to same conclusion some time ago.
I like it, it use it. But I think they are running out of ideas. Adding gradient to it is a joke IMHO. You basically have to add a bunch of classes just to control the gradients. As if I can remember all that. I think the utility classes should stay utility, should be simple and nothing beyond that. Leave the rest to custom code when necessary.
Thanks for sharing your experience with Tailwind. I've been thinking about learning it but had some questions in my mind. Like you said, the best thing to do is playing around with it and decide if that's a good one to use or not.
Exactly. They recently published play.tailwindcss.com/ - you can try it out with no setup whatsoever and play around with the classes & config!
Oh this is great! Thanks!
I never liked CSS frameworks. For the following reasons:
Great article, i want share these tricks!
Thank you for your tips! I still have things to look into and your suggestions seem promising 🙂
Thanks for asking! Not as of now as I rather try to extract the markup to different functions/partials/components (whatever you want to call it) and use them that way. I also try to follow the advice that's out there:
But I'm curious to see how useful the feature of component classes will be in the future for me
You could learn something really useful instead of wasting time on the tailwind. I mean it!