3 ms·
The common arguments against Tailwind usually derive from total ignorance of working with CSS on large scale projects with many team members. And when this is
by u_fucking_dork 5mo ago
The common arguments against Tailwind usually derive from total ignorance of working with CSS on large scale projects with many team members.
And when this is pointed out you’ll usually get replies that just hand wave it away as not a problem, as if things like BEM were invented for no reason.
- timr 5mo agoYeah, that's a straw-man. I've worked on large-scale projects with many team members, and it's perfectly possible to use CSS as it was designed. But sure, like most tools, it starts with understanding how it works.
- pverheggen 5mo agoSure, but "total ignorance of how CSS is made to work" is also a straw man.
- deleted 5mo ago[deleted]
- 9dev 5mo agoSure it's possible, but is it possible for everyone on your team? Including the new hire, the interns, or the now-vibecoding managers? Sooner or later it deteriorates.
- miyoji 5mo ago> Sure it's possible, but is it possible for everyone on your team? Including the new hire, the interns, or the now-vibecoding managers? Why aren't we asking this about any of the things that are actually hard? Like any programming language, or databases, or caching... CSS is the easiest part of the web stack.
- 9dev 5mo ago> Why aren't we asking this about any of the things that are actually hard? We do. That's what countless abstraction layers, linters, frameworks, style guides, and CI checks are for. > CSS is the easiest part of the web stack. …and because programmers keep thinking that, they stay ignorant about CSS and structuring the styles properly - leading to the problems I described above.
- u_fucking_dork 5mo ago“That’s a straw man”, he says, as he hand waves it away as if it were not a problem