Tailwind always reminds me that there’s this weird respect pitfall where people treat CSS as too hard / primitive to learn and then spend considerably more time trying to avoid writing it than it would have taken to learn the tools of their chosen trade.
Especially in the modern era, it’s not that hard – what takes time is building a custom design, and that’s a key point he’s missing in this article. If you want to look different than other Bootstrap sites, you can do the same customization work as in his Tailwind example. It’s also likely the case that thinking about how to name things is going to be better than just spraying utility classes long-term since that gets you to think about where things are and are not the same.
I was going to say this. Tailwind always appeared to be as an alternate way of writing inline styles. I focus mostly on the back end and CSS is always a source of frustration when dabbling in front end, so perhaps I am not the right target anyway.
might as well just use styles directly?