Tailwind CSS might not be for you
Disclaimer: This article is my version of Tailwind CSS: Adds complexity, does nothing. I respect the original author’s opinions, but I think there’s a better way to criticize Tailwind CSS. Here goes. If you work in the front-end, you’ve probably heard a lot about Tailwind CSS, a CSS framework, much like Bootstrap. Much unlike Bootstrap, however, Tailwind takes a different approach – it is almost e
TailwindCSS: Adds complexity, does nothing.
If you work in the front-end, you've probably heard a lot about TailwindCSS, a CSS library, much like Bootstrap. Much unlike Bootstrap, however, Tailwind takes a different approach - it is all "utility classes". And I am not a fan. I got a whiff of it and quickly learned the name is appropos: it was as welcome and useful as passed gas. Before we start, let me try to explain what a utility class is
Sexism, Racism, Toxic Positivity, and TailwindCSS
You might think that these things don't belong in the same article, but here we are, this week in front-end development, having the same conversation that seems to be never-ending. There's a complexity here that I find is being painfully pushed aside to focus on one thing: TailwindCSS versus... not TailwindCSS. In defense of TailwindCSS I want to start by saying that I am using TailwindCSS profess
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
