I don’t get it either. Start putting css in the style attribute while you’re at it.
BUT! This proves there isn’t a “right” way to do things and developers have differing preferences—enough to make 7 figures of revenue.
BUT! This proves there isn’t a “right” way to do things and developers have differing preferences—enough to make 7 figures of revenue.
I think everybody reacts like this at first (including me) :) If you put styles directly in the attribute, nothing is preventing your from using a color that's not part of your palette, nor using sizes that do not respect your UI "flow". Tailwind comes with a (customizable at build time) well-defined sets of colors and sizes.
I recommend watching the 17-minutes long talk "In Defense of Utility-First CSS" for those curious about Utility-First CSS: https://www.youtube.com/watch?v=R50q4NES6Iw