Cher has written an excellent, concise, and extremely
evenly-handed response to the current Tech Twitterβ’ nonsense. I
wanted to save it (alongside Andy's) to refer to next time this
happens β¦
π
Classic rock, Mario Kart, and why we can't agree on Tailwind
Josh may have written the perfect article on Tailwind. As
someone who has also spent quite a lot of time (both professionally
and personally) working with Tailwind, I couldn't agree more, β¦
I've never understood the appeal of TailwindCSS. I've watched
friends and colleagues get amped for it, seen their code, and just
felt like it was a meaningless abstraction of the existing
technology. β¦
An excellent overview from Josh of the pitfalls of using UI
frameworks. I particularly enjoyed their focus on why
developers often advocate for these tools, and how those needs are
often β¦
It will (hopefully) come as no surprise that I found myself
nodding vigorously throughout this excellent article by Elaina,
which shines a light on some of the reasons that CSS tooling can
leave a β¦
I have used Tailwind on various projects. I think for
prototyping and quick proof of concepts, for one-off projects that
never need to be updated, it has some advantages. But for code that
you want β¦
As acerbic and cutting a critique of utility-first CSS
(and that particular framework) as you would expect
from Heydon, but hidden amongst the humour are some (also equally
expected) jewels β¦
Tech Twitterβ’ is bickering again and, as ever, Andy's take is
the best take: use what works, understand that criticism is not an
attack, and realise that what works for you may not work for β¦
I've always thought the utility of Tailwind was
promising, but it bugged me that the way it worked was so counter
to both best practices and the web stack's architecture. Well,
introducing β¦