> I wouldn't be able to count on my 2 hands how many times I've Googled the term tailwind line-height, because of course, it's leading and I keep forgetting that.
Me too! Some being text, others font, is one that constantly trips me up.
I made this as I couldn't stand writing another 2K lines css file and wanted to try the atomic css wagon without having to switch from preact or having to learn tailwind
Happy to see a new CSS-in-JS lib. All of this madness about runtime performance costs does not apply to 99.9% of the population. But good abstractions do. And then there's latency, and machines are getting faster, and browsers getting better, etc etc. This whole argument and the related FUD was all a non-issue to begin with, at the great cost to DX.
> I wouldn't be able to count on my 2 hands how many times I've Googled the term tailwind line-height, because of course, it's leading and I keep forgetting that.
Me too! Some being text, others font, is one that constantly trips me up.
I also did some experiments in this space as I have the same complaints about Tailwind
https://github.com/aziis98/preact-css-extract
I made this as I couldn't stand writing another 2K lines css file and wanted to try the atomic css wagon without having to switch from preact or having to learn tailwind
Happy to see a new CSS-in-JS lib. All of this madness about runtime performance costs does not apply to 99.9% of the population. But good abstractions do. And then there's latency, and machines are getting faster, and browsers getting better, etc etc. This whole argument and the related FUD was all a non-issue to begin with, at the great cost to DX.
I encourage you to read the short paragraph at https://www.w3.org/TR/html-design-principles/#priority-of-co...