3 ms·
Offtopic, but I've googled Tailwind because of this comment. This seems absolutely crazy to me, in the worst sense imaginable. So, there was (and still is) "sty
by krick 4y ago
Offtopic, but I've googled Tailwind because of this comment. This seems absolutely crazy to me, in the worst sense imaginable. So, there was (and still is) "style" attribute in HTML. It leads to lots of repetition and yadda yadda, so people started using classes instead to write their CSS. There are dozens of schools of "best practices", or meta-frameworks, or actual frameworks to make it all more manageable, but now typically each element still has like 5 different classes specifically to define styles. So, finally someone got tired of it and came up with an ingenious solution: JS framework that dynamically defines CSS-classes with CSS-property-like names to write styles right in the HTML again, but to use class attribute instead of style attribute?! What's even the point?!
- davepeck 4y agoHah! This was pretty much my response when I encountered Tailwind for the first time. This post by Tailwind’s author gives some more perspective: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ https://adamwathan.me/css-utility-classes-and-separation-of-...
- arran-nz 4y agoI had the same concern, this article perfectly captures the problem and gives perspective to the solution Tailwind provides - Thanks for sharing!
- agumonkey 4y agoClasses are not perfect, they introduce relative meaning (or meaninglesness) and in prototyping its often a huge waste of time. Other than that I agree.