🤷 I would take your Tailwind CSS takedown piece more seriously if your blog weren't shilling something like your "perfect" web framework, CSS book, or paid course. We should come up with bingo cards for this stuff.
✨ Use the CSS framework, un-framework, or don't use a framework if that sparks joy.
🦄 There are no unicorn CSS solutions out there that solve everyone's problems. Vanilla CSS is good. Tailwind CSS is good. Your homegrown, hybrid, atomic solution is good, too.
@webology this. There are trends in the industry that are actively doing harm (hurting accessibility, wasting carbon for no reason). Tailwind isn’t for me, but neither are religious wars. Let people get work done.
@greg Their previous argument linked up the uncompressed CSS files while claiming that TailwindCSS is >30M and ya. Dishonest AF.
My issue with these is we could have good discussions about legit Tailwind CSS issues, but instead, we get dishonest hot takes to shill a CMS, book, etc.
@grantmc I'm 90% sure this is for the clicks and shilling of the previously mentioned things. Otherwise, I wonder why someone would call something dangerous and wrong, and then when I look at what they consider good, they look the same to me but with different naming conventions. It's unhealthy IMO.
@webology@onelson Just bought it, and getting comfortable using it. It's worth it, in my mind. Stuff like every-layout.dev, cubecss.fyi, utopia.fyi, and HTMX has brought back the joy in web development for me.
@bobschi@onelson, that's wonderful to hear. I'm a big fan of Andy Bell's work. It goes back over a decade and I should probably just buy the darn thing already. 🤣
Add comment