The problem with development in general these days is people like taking shortcuts. The mantra of "deliver fast" has clouded the (at least) equally important principle of "deliver quality". Tailwind and similar stuff are great for fast prototyping, but then again these prototypes tend to become "Minimum Viable Product" and therefore slips into production. And the nasty prototype code sticks in the product codebase through all production releases forever.
Efficiency is one (good) thing, but laziness is a totally different thing.
Tailwind just destroys a lot of good code design philosophies, and this article has pointed out many of them quite nicely. So I agree with this article and disagree with comments implying that this article is pure badmouthing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The problem with development in general these days is people like taking shortcuts. The mantra of "deliver fast" has clouded the (at least) equally important principle of "deliver quality". Tailwind and similar stuff are great for fast prototyping, but then again these prototypes tend to become "Minimum Viable Product" and therefore slips into production. And the nasty prototype code sticks in the product codebase through all production releases forever.
Efficiency is one (good) thing, but laziness is a totally different thing.
Tailwind just destroys a lot of good code design philosophies, and this article has pointed out many of them quite nicely. So I agree with this article and disagree with comments implying that this article is pure badmouthing.