Explore >> Select a destination
|
You are here 
|
frontendfoc.us | ||
| | | | |
gomakethings.com
|
|
| | | | | Over the last week or two, I've written about why Tailwind is bad. Yesterday, I stumbled upon this article from Tero Piirainen comparing semantic CSS to Tailwind... Semantic version is 8 × smaller, renders faster, and requires no JavaScript bundlers / tooling. The article is fully of wonderfully quotable statements, like this... Tailwind needs significantly more coding because you are completely lacking the power of CSS: the way it cascades and the richness of the selectors. | |
| | | | |
mxstbr.com
|
|
| | | | | Why Tailwind is blowing up, why I (the creator of styled-components) love it and how I avoid the downsides of atomic CSS. | |
| | | | |
8yd.no
|
|
| | | | | Write CSS as CSS in CSS. It is the best way to learn, and it gives us the best code quality because it leans on language and platform. Anything else tends to turn out not to be CSS at all, maybe fa... | |
| | | | |
windicss.org
|
|
| | | Next generation utility-first CSS framework. | ||
