There is a natural tendency to try reinvent something when you don’t understand it enough to be comfortable with it. Then that new thing lacks the maturity and scrutiny that the old thing went through to survive the test of time.
While this is something that does happen, there’s also a tendency for people in the industry to dismiss new things without actually looking into the pros and cons.
Doesn’t it give you pause that many very experienced Frontend & CSS developers see objective advantages in Tailwinds utility class approach? Of course there are also objective disadvantages, don’t get me wrong. But that means that these tools should be used whenever their advantages can shine and their disadvantages don’t cause issues.
Any developer that can’t clearly name the issues with regular CSS that Tailwind attempts to solve either hasn’t been developing long enough to encounter these issues, or hasn’t actually tried to understand what Tailwind is.
Doesn’t it give you pause that many very experienced Frontend & CSS developers see objective advantages in Tailwinds utility class approach?
That is not a good enough reason to justify its existence. You can very well say that fossil fuel companies should continue to exist because look at how long it’s been around with all the expertise people have. Surely they should stay around, right?
IMO, the industry decided to take the wrong direction, which I would agree makes sense from an economics perspective, but man, all I see is short term gains over long term ones, where we would’ve been able to build better solutions than hacks upon hacks (not using that fully derogatorily tbh). We could’ve spent all that energy, money, and time to bettering CSS and improving education to help people understand the cascade and specificity, while building better, more computationally efficient solutions that would minimize our bundles better and make JS a lot tamer than it is.
While this is something that does happen, there’s also a tendency for people in the industry to dismiss new things without actually looking into the pros and cons.
Doesn’t it give you pause that many very experienced Frontend & CSS developers see objective advantages in Tailwinds utility class approach? Of course there are also objective disadvantages, don’t get me wrong. But that means that these tools should be used whenever their advantages can shine and their disadvantages don’t cause issues.
Any developer that can’t clearly name the issues with regular CSS that Tailwind attempts to solve either hasn’t been developing long enough to encounter these issues, or hasn’t actually tried to understand what Tailwind is.
That is not a good enough reason to justify its existence. You can very well say that fossil fuel companies should continue to exist because look at how long it’s been around with all the expertise people have. Surely they should stay around, right?
Please also see my other comment
https://vger.to/lemmy.ca/comment/20657420
IMO, the industry decided to take the wrong direction, which I would agree makes sense from an economics perspective, but man, all I see is short term gains over long term ones, where we would’ve been able to build better solutions than hacks upon hacks (not using that fully derogatorily tbh). We could’ve spent all that energy, money, and time to bettering CSS and improving education to help people understand the cascade and specificity, while building better, more computationally efficient solutions that would minimize our bundles better and make JS a lot tamer than it is.
But I’m blabbering.