DEV Community

Discussion on: Tailwind. My experience using it for a month now.

Collapse
rahulh123 profile image
Rahul

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.

Collapse
gsarig profile image
Giorgos Sarigiannidis • Edited on

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.