@alper thinking developer experience is more important than user experience and that current ease trumps future tech debt seems like an entitled position.
@dams@estelle I get the impression what drove webdevs to Tailwind is when they're fighting their teammates selector specificity. At which point the cascade becomes unpredictable.
That said with Cascade Layers being supported everywhere, this should not be a problem anymore...
@kagan@estelle what about people like me? i'm primarily a backend developer with a full time job, partner, hobbies, etc. and i just don't have the time to learn all of the nuances of CSS, especially given the speed at which frontend seems to evolve.
Tailwind let me feel comfortable redesigning my personal site completely from scratch so much faster than i otherwise would've been able to do.
You don't have to learn all the nuances of CSS. I work with CSS everyday since years and I probably know only 40% of it and I can tell you that knowing only 5% is enough.
As a side note, Tailwind is CSS so using it implies you know what you are doing which also implies you know CSS. Unless you are randomly adding a ton of class names in a hope that it will work like you want (yes, many are doing this unfortunately)
Add comment