Classic rock, Mario Kart, and why we can’t agree on Tailwind
joshcollinsworth.com
Classic rock, Mario Kart, and why we can’t agree on Tailwind
1–10 of 44 posts
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#2As I commented on Mastodon:
Today's "Tailwind-in-HTML" is tomorrow's tech debt on a scale we haven't seen since the AngularJS days from a decade ago.
It won't be pretty.
(But perhaps a future job opportunity for folks who can rebuild design systems using real CSS and web standards.)
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#3Tailwind is the modern equivalent of Bootstrap.
Most teams do not have a dedicated designer. Most developers are quite bad at CSS. These teams, which are most teams, want to ship something that is not butt-ugly and do it fast.
That's what Bootstrap did and what Tailwind does. All the endless discussions about the technical merit of inlining utility classes versus hand-crafting CSS are pointless and cannot be resolved because they miss the point entirely.
The point is: ship something good-looking very fast by people that suck at UI or don't have proper time for it.
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#4I don't get tailwind at all. I never pressed the play button in terms of the article, but it's like promoting the use of MS Word without formatting styles... You end up with masses of shitty documents formatted with a wild mix of overlapping formatting options and extra spaces.
And yes, I am looking at you, Mom... ;)
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#5As I commented on Mastodon: Today's "Tailwind-in-HTML" is tomorrow's tech debt on a scale we haven't seen since the AngularJS days from a decade ago. It won't be pretty. (But perhaps a future job opportunity for folks who can rebuild design systems using real CSS and web standards.)
I don’t use it but what I think is cool about it is: if you use it with inline JavaScript you never have to think about separation of concerns ever again.
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#6As I commented on Mastodon: Today's "Tailwind-in-HTML" is tomorrow's tech debt on a scale we haven't seen since the AngularJS days from a decade ago. It won't be pretty. (But perhaps a future job opportunity for folks who can rebuild design systems using real CSS and web standards.)
Between Tailwind and htmx, we can probably run Doom in HTML attributes.
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#7So the takeaway for me here is to avoid dogma, and if your “senior” coworkers are forcing it on you, leave asap. Oh and if you want to be productive, use Tailwind first and hand craft the small percent of CSS where that’s required later, if such a thing actually occurs. Everything else is just religion (in the emacs vs vim sense).
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#8Tailwind is the modern equivalent of Bootstrap. Most teams do not have a dedicated designer. Most developers are quite bad at CSS. These teams, which are most teams, want to ship something that is not butt-ugly and do it fast. That's what Bootstrap did and what Tailwind does. All the endless discussions about the technical merit of inlining utility classes versus hand-crafting CSS are pointless and cannot be resolved…
Bootstrap is still here. Tailwind CSS just gives more freedom, and no elements out of the box - you have to do it yourself. Both are great tools to build a landing page or a website fast.
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#9Tailwind is the modern equivalent of Bootstrap. Most teams do not have a dedicated designer. Most developers are quite bad at CSS. These teams, which are most teams, want to ship something that is not butt-ugly and do it fast. That's what Bootstrap did and what Tailwind does. All the endless discussions about the technical merit of inlining utility classes versus hand-crafting CSS are pointless and cannot be resolved…
I don't think this is right at all. Tailwind comes with no opinions about your styles other than their default units of length (p-1, p-2, p-3) having a set REM scaling. Perhaps you're thinking of e.g. DaisyUI [0]? Or some other CSS framework built on Tailwind?
Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind
#10I've been working in CSS for over 20 years. I know it very well. Tailwind is also my absolute most favorite technology to come along in a long time. I would even argue to use it effectively you also need to understand CSS well. The smart steering analogy doesn't jive with me at all.