There’s been a lot of buzz recently about things like Tailwind and functional/utility-first CSS (for more on that, check out JSParty #65 with the creator of Tailwind), but there has also been some pushback against the approach. This article spells out some of the concerns, and why this may be more of a reaction against learning CSS than a new best practice.

Author Jay Freestone, after summing up a series of challenges:

In summary, functional CSS doesn’t make much sense to me, as a front-end developer. I’d suggest that a dedicated front-end team would be more productive managing their own CSS approach, rather than being tied into the straitjacket of a standardised class library.