CSS Utility Classes and “Separation of Concerns” (2017)

Re:CSS Utility Classes and “Separation of Concerns” (2017) by csande17 on Saturday November 16, 2019 @01:52PM (#21554245)

At least React's "pass an object to the `style` prop" makes it relatively easy to do that overriding.

With utility classes, your code has no way of knowing that "bg-red" should override "bg-blue". (And frequently it won't, if "bg-blue" happens to come later in the CSS file.) So people end up inner-plaforming their own clunky solutions on top.

[ Parent | on HN ]

Re:CSS Utility Classes and “Separation of Concerns” (2017) by mxstbr on Saturday November 16, 2019 @03:01PM (#21554609)

You would be surprised how many people do not know that the order of classes in the source file, not the class="" attribute, matters.

See my (totally unscientific, yet scary) poll of my audience, which heavily leans towards frontend with a focus on React: https://mobile.twitter.com/mxstbr/status/1038073603311448064...

Only 43% got it correct!

[ Parent | on HN ]

Re:CSS Utility Classes and “Separation of Concerns” (2017) by jeltz on Saturday November 16, 2019 @03:51PM (#21554874)

If you do not know basic stuff like that how can you even write CSS at all? Trial and error?

[ Parent | on HN ]

Re:CSS Utility Classes and “Separation of Concerns” (2017) by Izkata on Saturday November 16, 2019 @04:23PM (#21555044)

From experience with co-workers: Yep, and lots of !important

[ Parent | on HN ]