That's source code from the project. Tailwind is just inline styles via CSS shorthand classes. I cannot understand why anyone would want this unless they are coming from bootstrap.
Tailwind is unreadable when glancing through source code, especially when styles get large. It's just a web fad.
padding 48, on small screens vertical padding 32 and horizontal padding 24, center styled? try doing that inline....
i always see this and never understand the pushback, or have people never worked on large apps spanning hundreds/thousands of components and have to maintain it.
it's a godsend when working on older components and i don't have to dig thru some other css file and figure out exactly how and why i named it. inline css doesn't allow to do transitions, animations, responsive breakpoints, etc. everything is there is contextual and i never break flow going from design to implementation. you still can have global styles or can have a master design guide.
hunterb123|4 years ago
That's source code from the project. Tailwind is just inline styles via CSS shorthand classes. I cannot understand why anyone would want this unless they are coming from bootstrap.
Tailwind is unreadable when glancing through source code, especially when styles get large. It's just a web fad.
alunchbox|4 years ago
A big one is that you don't have to think about abstractions or relationships between classes.
But instead think in terms of utility and really making it a language of it's own right.
I was hesitant but gave it a go. It was quite enjoyable and productive.
There's also the @apply which enabled you to still remove the duplication or build your own utilities on top of their skeleton.
Don't knock it till you try it!
steve_adams_86|4 years ago
It's gaining momentum and it has been around for 4 years (https://adamwathan.me/going-full-time-on-tailwind-css/, https://github.com/tailwindlabs/tailwindcss/commit/421c1b0d7...)
It was preceded by other similar frameworks, too. It's a pattern some people like, and it's productive enough that I suspect it'll stick around.
ookblah|4 years ago
i always see this and never understand the pushback, or have people never worked on large apps spanning hundreds/thousands of components and have to maintain it.
it's a godsend when working on older components and i don't have to dig thru some other css file and figure out exactly how and why i named it. inline css doesn't allow to do transitions, animations, responsive breakpoints, etc. everything is there is contextual and i never break flow going from design to implementation. you still can have global styles or can have a master design guide.
beckler|4 years ago