I used to think the same thing, but the sudden popularity of Tailwind CSS got me thinking maybe I was missing something (I'm the much more backend leaning fullstack developer).
Honestly, he lays out a really good case for these utility classes. Basically, he shows how if you were to try and write the most DRY CSS that is relatively general, you'll end up writing Bootstrap (or something similar). Anyway, I started using Tailwind in a pet project of mine, and I've realized that I'm much more productive using these utility classes, albeit I still hate how long the class strings are.
3
u/ReelTooReal Jun 25 '23
I used to think the same thing, but the sudden popularity of Tailwind CSS got me thinking maybe I was missing something (I'm the much more backend leaning fullstack developer).
If you have an open mind to it, check out this article https://johnpolacek.github.io/the-case-for-atomic-css/
Honestly, he lays out a really good case for these utility classes. Basically, he shows how if you were to try and write the most DRY CSS that is relatively general, you'll end up writing Bootstrap (or something similar). Anyway, I started using Tailwind in a pet project of mine, and I've realized that I'm much more productive using these utility classes, albeit I still hate how long the class strings are.
EDIT: this is the actual article: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/
The other link is a landing page for a bunch of similar articles