I’m so tired of y’all web people hating on #Tailwind. You're not funny, it’s just the same kind of disrespect you call out in many other cases. Why can't we just accept that there is no right™ way to do #CSS (or anything, really) and stop shitting on each other for using technology we personally dislike for whatever reason.
“If your development tool doesn’t allow you to split your code into components, it’s likely that the utility-first approach of Tailwind will only make development harder...
“And... avoid using the @apply directive... It throws away the key advantages of Tailwind: less mental overload when coming up with names for CSS classes, and the absence of regressions when changing styles... Further, using it increases CSS bundle size.”
Happy to merge a pull requests, that adds the runserver_plus command from django-extentions to my #django#tailwind extension django-tailwind-cli. A handy addition provided by William Hayes.
In #tailwind, is there a way to set the font size every <h1> tag to e.g 2 rem by default? Without having to add a class name to every tag?
I’ve been trying to do it in the tailwind.config file using the typography plugin, thus far without success. I can’t work out if it’s not possible or if I just don’t understand the documentation.
It's popular to say we can’t agree on Tailwind, but I posit we actually already do. I think what we actually disagree on isn’t the details of this (or any) specific software; it's in what we value, and how we each define assets and liabilities.
I think this hits the nail on the head. This is precisely my issue with #tailwind. It actively ignores one of the most powerful aspects of #CSS:
“I think that Tailwind might be a good example of an imperative design tool. It’s only about the specific outputs. Systematic thinking is actively discouraged; instead you say exactly what you want the final pixels on the screen to be.”
@keithjgrant Took a look. Looks interesting. #css did evelove since the last time I wrote raw css.
Nevertheless, I feel like #tailwind is faster in development, and I don’t need to maintain any css files.
I just like pelo who trash tailwind, used it to build a simple todo app, and concluded that it’s like raw style tags, while in reality tailwind offers way more utilities
I personally find Tailwind productive, but I think the author is right: it's a tool that will become redundant at some point as the state of CSS advances (much like jQuery was made redundant by modern vanilla JS).
Whilst most of the #tailwind#css posts I’ve read have all been, “Could it be possible! This old saint in the forest hath not yet heard of it, that God is dead!”, this one is quite good.
There's a worrying trend in modern web development, where developers are throwing away decades of carefully wrought systems for a bit of perceived convenience. Tools such as Tailwind CSS seem to be spreading like wildfire, with very few people ever willing to acknowledge the regression they bring to our field. And I'm getting...
Tailwind is great. Y'all love to overcomplicate things. I hope this helps you keep them nice and simple#tailwindcss #webdevelopment ALL MY VIDEOS ARE POSTED ...
Is it spicy to cite the #HTML specification when talking about #Tailwind? rounded-xl, dark-sky-500, and so on totally goes against the advice of the specification for appropriate class values for #CSS.
#Tailwind, and the death of web craftsmanship: "Tailwind is a symptom a rapid deterioration in pride-of-craftsmanship in development. It's naive to believe that "back in the old day" everyone wrote everything with a perfect eye towards beautiful craftsmanship… but there was definitely more interest in "doing it right" rather than dismissing it as a problem that wasn't worth solving." #CSShttps://pdx.su/blog/2023-07-26-tailwind-and-the-death-of-craftsmanship/
🌶️ Spicy tip: if you don't know how to write performant, maintainable #CSS for your web project without giving up and slapping #Tailwind on it, that's not on the platform. That's on you.
But don't worry! 😃 There are many fantastic resources for learning how to write vanilla CSS out there, and we're just about ready to release our own. Once you know it, you know it. And you can apply it to any reasonable web stack until the end of time. 🙌
Small update to our experimental tool Vanilla Breeze which lets you convert #Tailwind#CSS markup to CSS and HTML — no, not by supplying you with a stylesheet filled with utility classes (as TW does), but by converting the TW theme to CSS variables and then generating an actual stylesheet which applies CSS rules & variables to the DOM structure itself. This is your “escape hatch" to take a TW component and use it outside of TW!
@andy@heydon When you are working with #tailwind do you utilise the three base/component/utility layers? If so, how do you map the additional categories? Par exemple...
reset/global styles to base
composition (layout primitives )/block to components
then piggyback on tailwind for the utility classes? #css
Classic rock, Mario Kart, and why we can't agree on Tailwind (joshcollinsworth.com)
It's popular to say we can’t agree on Tailwind, but I posit we actually already do. I think what we actually disagree on isn’t the details of this (or any) specific software; it's in what we value, and how we each define assets and liabilities.
Tailwind, and the death of web craftsmanship (pdx.su)
There's a worrying trend in modern web development, where developers are throwing away decades of carefully wrought systems for a bit of perceived convenience. Tools such as Tailwind CSS seem to be spreading like wildfire, with very few people ever willing to acknowledge the regression they bring to our field. And I'm getting...
I WISH I Knew These Tailwind Tips Earlier (youtu.be)
Tailwind is great. Y'all love to overcomplicate things. I hope this helps you keep them nice and simple#tailwindcss #webdevelopment ALL MY VIDEOS ARE POSTED ...