Designer News
Where the design community meets.
over 7 years ago from Adam Silver, Interaction designer focused on inclusive design and design systems
This is more or less the opposite of how I think you should write css.
EDIT: I just realized this seems like a dick comment and I'm sorry, I'll try to expand when I get off work.
Agreed. The more I think about it, the crazier it sounds. If anything, it goes against what it is trying to solve.
Same here. There's no evidence for any of this and most of the reasoning seems to be based around vague concepts like "semantics" and "bloat".
Nice to see an opposing point of view but I'm not convinced by any of the arguments presented in the "semantics" and "reuse" chapters.
I agree this is overly dogmatic, I think there's a happy medium here (in my experience at least) where you have objects as well as utility classes for common, repeatable styles e.g. something like Harry Roberts' ITCSS.
I've started using pure utility classes a lot recently (with responsive suffixes eg @m
) and find this a really nice way to express simple bits of layout, type and whitespace.
I don't understand this at all:
If you have utility non-semantic classes that describe the look then when you edit one of these classes, they will propogate to every single element with that class
That's the whole point of utility classes, they follow the single responsibility principle and you would be incredibly unlikely to edit them.
Designer News
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
Have feedback?
Clearly, the author of that resource has never worked with large apps—how is that scalable?