5 ms·

tailwindcss is such a godsend when it comes to styling. To anyone glancing at it thinking "this is trash it's just inline styles all over the place that encoura

tailwindcss is such a godsend when it comes to styling. To anyone glancing at it thinking "this is trash it's just inline styles all over the place that encourages duplication" I implore you to actually read and think about the points raised here: https://adamwathan.me/css-utility-classes-and-separation-of-concerns/ https://adamwathan.me/css-utility-classes-and-separation-of-... tailwindcss effectively boils the dauntingly large control plane of every CSS feature down into "utility classes" that you then compose all styling from. So far, it has had a solution for every styling problem I have encountered, and in the cases it didn't, when I really thought about it I was trying to do something dumb anyway. I swear I am not affiliated with the project at all haha, I just felt such a relief after giving it an honest try on a project and I could very easily see how powerful it would be in many of my past projects had we access to it (and convinced the naysayers)

wildrhythms 6y ago
lol I've seen many reactionary takes in my workplace from front-end engineers (or even on Hackernews) reacting to Tailwind as "this is just inline styles with extra steps!" ... no, "inline styles with extra steps" is what you're doing now with CSS: writing a hundred one-off ".container" classes and bundling that with a hundred other ".container" and ".wrapper" classes across a hundred different components in the app. Tailwind is revolutionary. It has completely changed the way I develop, and I will evangelize it at every opportunity. I've started migrating a major project to Tailwind, and for the first time I'm not horrified by having to deal with conflicting stylesheets, etc. Everything I need to know about how a component looks is kept in the component, where it should be, and the bundle size is smaller than ever because Tailwind can prune the styles down to exactly what I'm using. Tailwind is great, and shoutout to Adam Wathan's youtube channel- very helpful in learning how it works and convincing me to try it.
- vinger 6y ago
  Adam's success is a podcast success story. The patience required to slowly build up an audience by creating daily videos/postcasts that incrementally built an application or framework. Adam had success time and again but he always builds profits and abandons. PHP without loops, test driven laravel are two other successful audiences that were built, sold to and abandon. He has seemed to move on from refactoring ui. It has been a year+ since Tailwinds has been released. How much longer before Adam jumps to the next thing?
  - corytheboyd 6y ago
    What’s wrong with him pursuing other projects. Creators aren’t restricted to only maintaining the first thing they release for the rest of their lives. I will say I am a bit worried about their headless ui project, seems to have been in “early” development for a while and feels like something that maybe should have been ready by the time tailwindcss was. I’m just assuming that project is dead in the water, but it doesn’t matter so much to me because I get enough value out of just tailwindcss
lenkite 6y ago
Tailwind CSS makes complete sense for folks who are deeply conditioned to NPM hell and stockholm-syndromed to godzilla JS build processes that makes Heavy Enterprise Java look like a dancing hummingbird. The rest of us who like our lean mean HTML and CSS will stick to the old-school way of doing stuff - separating styles from our HTML with clean classes and markup with no need for a build step just to create basic stylesheets.
- corytheboyd 6y ago
  Ignoring your rude dismissal of the NPM ecosystem, do you actually create sizable web pages without some sort of build tool? How? Duplicating entire HTML documents and adjusting any relative paths, etc.? I’m really not trying to attack your way of doing things and “force” a “shitty” build process on you, but I often see this dismissal thrown around without any actual substance and it’s honestly getting very old.
  - lenkite 6y ago
    One can stick to plain and fast SSGs without bringing NPM into the picture. Maintain dependencies in your repository. I think there is extraordinary evidence been presented over the past several years to derive the judgement that NPM is terrible. It is a dismissal with very real and actual substance. One just needs to go through the several dozen critique on HN alone - all supported with a truckload of data, horrendous experiences and security vulnerabilities. Frameworks which marry themselves to this ecosystem are OK for those developers who are already in NPM hell. My apologies for your suffering - but the rest of us don't need to join the cult of doom.
Kagerjay 6y ago
I haven't used tailwinds much but one of it's flaws is that it doesn't support web accessibility out of the box, and it's javascript widget support is still in it's infancy I much prefer chakraui approach to building a design system library. It utilized many naming conventions based off of tailwinds

wildrhythms 6y ago

lol I've seen many reactionary takes in my workplace from front-end engineers (or even on Hackernews) reacting to Tailwind as "this is just inline styles with extra steps!" ... no, "inline styles with extra steps" is what you're doing now with CSS: writing a hundred one-off ".container" classes and bundling that with a hundred other ".container" and ".wrapper" classes across a hundred different components in the app. Tailwind is revolutionary. It has completely changed the way I develop, and I will evangelize it at every opportunity. I've started migrating a major project to Tailwind, and for the first time I'm not horrified by having to deal with conflicting stylesheets, etc. Everything I need to know about how a component looks is kept in the component, where it should be, and the bundle size is smaller than ever because Tailwind can prune the styles down to exactly what I'm using. Tailwind is great, and shoutout to Adam Wathan's youtube channel- very helpful in learning how it works and convincing me to try it.

vinger 6y ago
Adam's success is a podcast success story. The patience required to slowly build up an audience by creating daily videos/postcasts that incrementally built an application or framework. Adam had success time and again but he always builds profits and abandons. PHP without loops, test driven laravel are two other successful audiences that were built, sold to and abandon. He has seemed to move on from refactoring ui. It has been a year+ since Tailwinds has been released. How much longer before Adam jumps to the next thing?
- corytheboyd 6y ago
  What’s wrong with him pursuing other projects. Creators aren’t restricted to only maintaining the first thing they release for the rest of their lives. I will say I am a bit worried about their headless ui project, seems to have been in “early” development for a while and feels like something that maybe should have been ready by the time tailwindcss was. I’m just assuming that project is dead in the water, but it doesn’t matter so much to me because I get enough value out of just tailwindcss

lenkite 6y ago

Tailwind CSS makes complete sense for folks who are deeply conditioned to NPM hell and stockholm-syndromed to godzilla JS build processes that makes Heavy Enterprise Java look like a dancing hummingbird. The rest of us who like our lean mean HTML and CSS will stick to the old-school way of doing stuff - separating styles from our HTML with clean classes and markup with no need for a build step just to create basic stylesheets.

corytheboyd 6y ago
Ignoring your rude dismissal of the NPM ecosystem, do you actually create sizable web pages without some sort of build tool? How? Duplicating entire HTML documents and adjusting any relative paths, etc.? I’m really not trying to attack your way of doing things and “force” a “shitty” build process on you, but I often see this dismissal thrown around without any actual substance and it’s honestly getting very old.
- lenkite 6y ago
  One can stick to plain and fast SSGs without bringing NPM into the picture. Maintain dependencies in your repository. I think there is extraordinary evidence been presented over the past several years to derive the judgement that NPM is terrible. It is a dismissal with very real and actual substance. One just needs to go through the several dozen critique on HN alone - all supported with a truckload of data, horrendous experiences and security vulnerabilities. Frameworks which marry themselves to this ecosystem are OK for those developers who are already in NPM hell. My apologies for your suffering - but the rest of us don't need to join the cult of doom.

Kagerjay 6y ago

I haven't used tailwinds much but one of it's flaws is that it doesn't support web accessibility out of the box, and it's javascript widget support is still in it's infancy I much prefer chakraui approach to building a design system library. It utilized many naming conventions based off of tailwinds