CSS's problems are Tailwind's problems
colton.dev
CSS's problems are Tailwind's problems
1–10 of 179 posts
Re: CSS's problems are Tailwind's problems
#2I used to be a naysayer of tailwind. However after getting practically forced into it I'm now drinking the koolaid. Yes things like having to duplicate styles using multi cursor is kind of silly, however for the vast majority of the time, having the styles written clearly each time, for me, makes it worth it.
There is also nothing stopping you mixing and matching.
Re: CSS's problems are Tailwind's problems
#3...then goes on to promote "CSS-in-JS"
Re: CSS's problems are Tailwind's problems
#4If you go even minimally outside the beaten path, the tailwind CSS declarations can mutate into a frankenstein monster that makes regular CSS look like a friendly, cute koala
Example: https://www.nikolailehbr.ink/blog/realistic-button-design-cs... shows an "old fashioned", 90's are back-in-vogue, 3d button.
Tailwind CSS for it becomes
After
Re: CSS's problems are Tailwind's problems
#5I can't take this article seriously since the recommendation is to use CSS-in-JS. Perhaps the worst CSS related invention ever, easily surpassing tailwind in it's awfulness.
Just use CSS modules. Just use CSS modules.
Re: CSS's problems are Tailwind's problems
#6If you go even minimally outside the beaten path, the tailwind CSS declarations can mutate into a frankenstein monster that makes regular CSS look like a friendly, cute koala Example: https://www.nikolailehbr.ink/blog/realistic-button-design-cs... shows an "old fashioned", 90's are back-in-vogue, 3d button. Tailwind CSS for it becomes After I got eye-strain and headaches after taking over maintenance of a tailwind ba…
I can't believe people find even half of this acceptable, do they never use a browser inspector in their work?
Re: CSS's problems are Tailwind's problems
#7I can't take this article seriously since the recommendation is to use CSS-in-JS. Perhaps the worst CSS related invention ever, easily surpassing tailwind in it's awfulness. Just use CSS modules. Just use CSS modules.
I'd really appreciate reading the whole article before commenting like this. I point out the problems with CSS-in-JS and do not wholly endorse it, and I do recommend using simple CSS as a solid solution for many people.
Re: CSS's problems are Tailwind's problems
#8I'm sure many still like Tailwind but I never liked it, maybe because I worked with pure CSS or SCSS for many years before it.
In the end its just another library that if you learn it well it will work for you and it has as many downsides as any other library ever used.
By the way the article seems a bit like an advertising for vanilla-extract library.
Re: CSS's problems are Tailwind's problems
#9I don't understand the point of the rule sets and constant classes? TailwindCSS still obeys the same specificity rules of CSS so instead of `font-medium` on every tag under nav why not just put `font-medium` on the parent tag?
Re: CSS's problems are Tailwind's problems
#10If you go even minimally outside the beaten path, the tailwind CSS declarations can mutate into a frankenstein monster that makes regular CSS look like a friendly, cute koala Example: https://www.nikolailehbr.ink/blog/realistic-button-design-cs... shows an "old fashioned", 90's are back-in-vogue, 3d button. Tailwind CSS for it becomes After I got eye-strain and headaches after taking over maintenance of a tailwind ba…
I used to be against Tailwind. Now that I've used long enough I can tell you that code is perfectly fine. I can read it and easily modify it. You can comment it out if you care
After