3 ms·
Good luck using pseudoclasses, pseudoelements or media queries in inline styles. Wrt Tailwind I still have not used it enough to decide whether it is good™ but
by afiori 3y ago
Good luck using pseudoclasses, pseudoelements or media queries in inline styles.
Wrt Tailwind I still have not used it enough to decide whether it is good™ but it is not that different from writing inline styles.
Apart from optional plugins it is more like a CSS preprocessor than a framework (every class expands to one or few CSS declaration)
The most frameworky features it has is that it predefines CSS variables to allow further customization
- wizzwizz4 3y agoIf you need any of those things, you should be using a proper stylesheet. Use <style scoped='scoped'> in the <body>, if you really must. A crude "not that different from writing inline styles" classy framework just makes it harder to refactor your CSS in future, because it's all tucked away under incomprehensibly-named CSS classes, and there are otherwise-useless <div>s all through the HTML.
- afiori 3y agoI should clarify that I primarily touch html via React, so the unit of reusability is not CSS but rather components. For handwritten html I believe that tailwind has significant downsides (unless you abuse @apply), but that the case I focus on. I should have mentioned that I believe tailwind to be applicable only if you have some strong templating support > Use <style scoped='scoped'> in the <body> This seems to have been removed from everywhere since at least 2017
- pwdisswordfishc 3y agoJoke's on you: I avoid inline CSS like the plague whenever I can. Which is to say, I use it as intended.
- afiori 3y agoThis does not suprise me, inline CSS is very unwieldy