3 ms·
I'm pretty good at CSS. Getting good at it is not a straight line with perfect logic, like say Python. Browser issues, different ways of doing the same thing, c
by Julesman 3y ago
I'm pretty good at CSS. Getting good at it is not a straight line with perfect logic, like say Python. Browser issues, different ways of doing the same thing, cascading in general. I get the issues. But a) we have no serious alternative at this point, and b) the answer isn't frameworks.
I hate CSS frameworks as much as coders hate CSS. Web architecture is fairly organized when you have HTML, CSS, and Javascript files. I appreciate the modular nature of React, but otherwise, frameworks like Tailwind basically entirely muddy that separation. I can no longer know whether the style of an element needs to be changed in the html or css file. And the html become much harder to read. That's just not better.
I know at some scale, with a very static design system, that Tailwind can speed up deployment. But half-decent semantic HTML with some custom helper classes can make Tailwind entirely unnecessary for most tasks.
I wake up every day happy I'm never using Bootstrap again. Say yes to CSS. lol
- datavirtue 3y ago"But half-decent semantic HTML with some custom helper classes can make Tailwind entirely unnecessary for most tasks." True but it never happens. Where is CSS going? Tailwind. Ninjas like you that want to tinker with CSS can work on tailwind...or bootstrap...or something else.