81–90 of 106 posts
How is tailwind different than Atomic CSS? https://acss.io Small utility classes without writing CSS, seems like the same thing. Disclaimer: I worked with the devs that created it.
Earlier quoted context omitted.
I mean a lot of those things were possible with bootstrap-sass years ago. > Define the essence of your design in a JSON - typography, colors, spacings, shadows, borders et al. _variables.sass > Anyone in the team including backend developers can create new interface components without waiting on a designer, thanks to well-defined scales that compose well. This is true, but is solved by any sort of component system an…
_variables.sass works if you're using BEM. But now you have two component-like things: BEM classes, and the components themselves. BEM solves the issues inherent in nested CSS (cascade, inheritance, multiple selectors, specificity) by forcing us to never nest them, and instead having to name every single element in HTML. Though they look semantic, they are not truly reusable since they are coupled deeply with the mar…
What's the difference between tailwind and tachyons?
You can generate tachyons from tailwind
For what it's worth, I don't think "What is Tailwind?" makes that clear (the "designed to be customized" section hints at it) and I had to read https://tailwindcss.com/docs/configuration to understand the difference after reading your comment. Thanks!
Earlier quoted context omitted.
Generally you’d have your button html and classes inside a component so you’re just tweaking that one component.
Then it feels like we're just back to writing normal CSS classes.
Earlier quoted context omitted.
_variables.sass works if you're using BEM. But now you have two component-like things: BEM classes, and the components themselves. BEM solves the issues inherent in nested CSS (cascade, inheritance, multiple selectors, specificity) by forcing us to never nest them, and instead having to name every single element in HTML. Though they look semantic, they are not truly reusable since they are coupled deeply with the mar…
BEM?
http://getbem.com/introduction/
In short, you do things like this:
.form { }
.form--theme-xmas { }
.form--simple { }
.form__input { }
.form__submit { }
.form__submit--disabled { }
Where the prefix __ is an Element and -- is a Modifier.
So, in that example you have the form, the form with Christmas modifier and also a form button that is expected to only happen under forms.
Earlier quoted context omitted.
You make interesting points. For me, as a back-end developer, the prevalence of Bootstrap is a major con because I can't (due to lack of knowledge or confidence, I'm not sure) make a Bootstrap site look like anything other than a Bootstrap site with different colors. Tailwind is the first front-end framework that successfully got me away from that and helped me execute own unique design vision. What seems to come to…
For websites where having a unique design is not a requirement or a priority, Bootstrap and similar frameworks are very helpful.
Earlier quoted context omitted.
To be fair, you can do that with SASS variables too and is not unique to Tailwind.
I've not seen people encouraging variables called $white, because that's pretty short sighted. It seems to be encourages with utility css
I think the big shift started to happen when people started to say, let’s treat CSS like code and what would we expect of good code, and then all of these CSS Sacred Cows were then seen in a new light. The biggest of them all for me was ‘naming things are hard’, traditional CSS implies naming your classes is easy, and for a once off example it is always easy, but that approach is a lifetime commmitmnet to generating names on names just to add styles and this adds a naming things complexity burden that until recently has just been a generally unacknowleged invisible cost.
It is convenient but you are not separating markup and presentation. I think the whole point of css is to swap stylesheets and get a different presentation, like demostrated by http://www.csszengarden.com/ BEM/OOCSS lets you do this.
How many times you do that in real project? Or have you ever done that in your career? And if a project needs substantial redesign it is usually acompanied by the functionality change, which means you need defferent html/components too, so you still can`t just swap css files.