Re:Tailwind CSS v3.3
by rimliu on Wednesday March 29, 2023 @08:53AM
(#35356516)
Separation content and style works perfectly well. Just people never bother to learn neither HTML nor CSS and rely on some generated monstrosity, be it generated by WP or React.
[ Parent
| on HN ]
Re:Tailwind CSS v3.3
by michaelcampbell on Wednesday March 29, 2023 @12:14PM
(#35359324)
It works for me mostly only theoretically. When I have to apply it at scale I run into the practical problems that people mention here; 1 big namespace, mostly.
Do you mean conflicts or spillovers?
Because, as I said elsewhere in the thread, I think (maybe wrongly) that simple linting could rid you of the vast majority of these problems.
But, please, if you mean something else, do comment! I very much like this discussion.
Re:Tailwind CSS v3.3
by michaelcampbell on Thursday March 30, 2023 @08:47AM
(#35371797)
For me I meant coming up with a name that semantically describes this area of the HTML, that I haven't already used.