|
|
|
|
|
|
by alan_n
997 days ago
|
|
|
I'm glad the writer has actually tried Tailwind and I respect it's not really their thing, but I've got to hard disagree with the Builder vs Crafter/specialist look on it. Tailwind will only just barely save you from not knowing CSS, it's still fundamental to understand it. Also I would consider myself very well versed in CSS, but while my handcrafted css works, it cannot compare in maintainability to its tailwind equivalent. CSS inevitably becomes a spaghetti soup of states after a while. I switched an entire component library to tailwind + tailwind-merge and everything was much cleaner and easier to understand. So much so I could not believe it. |
|
|
I think it happens eventually with most of code, whatever language. If you don't have a clear structure or methodology at the time of writing it, it will become a mess at some point. I don't think it's a particular problem of CSS.
So that unveils me as a "crafter" - well, am a graphic designer doing CSS since 2006 or so; in fact I've thought that way about doing 'raw' CSS, that is the most "artisanal" thing one can do in the world of web dev - and whereas it is true Tailwind can save time in styling a web page or whatever, it takes away from the expresiveness of doing it "by hand". Many people even here wonder from time to time why contemporary websites pretty much look the same: many people are using frameworks to style them.
It's kind of something like doing your own furniture in a pretty artisanal way vs. getting something from Ikea. Or more like growing your own potatoes vs. buying processed potatoes at a mall. You'll end with potatoes in your stomach, but they will taste differently.