@andrewfeeney @zachleat Well I can't read it. 🤷🏻♂️
I'll happily cop to being cognitively impared so that utility-classes-gone-wild can be seen as an accessibility violation. If all of this were in a co-located <style> tag as vanilla CSS, I could read that easily. 😊
Damn! That doesn't look like COBOL at all.
You spelled "Hello World" wrong.
@zachleat This toot needs a content warning. I am getting increasingly agitated just looking at all the utility classes.
I can just imagine the client asking message sections to have a slate 800 background instead of 900 and having to find and change it in dozens of files.
@thurti I think there is a lot to unpack here and I don’t go into making this joke without self awareness of what’s happening.
But I would ask: when did tooling tribalism become so that we can’t critique code? That a mere lighthearted humorous critique of code is a personal attack?
Finally the thing I always try to evaluate before making a joke like this: is it punching down? And no, I would very strongly argue that it is not.
@zachleat Sorry for being passive aggressive myself, I didn't mean to get personal. We should definitely criticize code. And there is a lot to criticize in this example.
I just got the feeling from reading the comments that all the tailwind and js bashing is becoming a cult itself.
@thurti no worries!
Yeah, I can see that criticism too. I have thought about it a lot. It’s easy to dismiss the criticism as a Nickleback style level-of-popularity pushback, but I think it goes deeper.
I think Tailwind in particular receives a lot of deserved criticism because they go pretty headstrong in their marketing almost to the point of being anti-CSS—specifically the line “best practices don’t work” that’s been on their home page for many years.
@olets @zachleat some valid points of criticism imo https://nuejs.org/blog/tailwind-misinformation-engine/