331–340 of 893 posts
Earlier quoted context omitted.
Every project I worked on that used CSS was a mess. It's always 1000 line SCSS files and nobody knows what is going on there.
> It's always 1000 line SCSS files and nobody knows what is going on there It's been 15-20 years since I last saw that. There are tons of solutions on how to easily organize CSS code these days that don't involve TW.
Very sad to hear, I bought Tailwind UI years ago and although it was a lot more expensive than I wanted, I've appreciated the care and precision and highly recommend buying it (It's now called Tailwind Plus) even still (maybe even especially now). Mad props to Adam for his honesty and transparency. Adam if you're reading, just know that the voices criticizing you are not the only voices out there. Thanks for all you'…
This book taught me so much about modern UI design. If you've ever tried building a component and thought to yourself, "hmm something about this looks off," you might benefit from this book.
These days some of the examples might be a little bit dated (fashions come and go), but the principles it teaches you are rock solid.
Earlier quoted context omitted.
Tailwind Plus is great - I love the lifetime access, but I always wondered how sustainable that model was. Even without AI, how many of those memberships could they sell?
I thought the same, and yet on the other hand, how could they have done it differently? People don't want to pay a subscription just to write a DSL of CSS. Perhaps they could've done it per project like some companies, but I don't think it'd be as popular as their lifetime model. Ironic.
Earlier quoted context omitted.
If there's anything AI coding is good at, it's writing react components and tailwind css.
If you want a bunch of tailwind class slop, then yes. Otherwise, A lot of context engineering is needed if you want it to write modular tailwind components properly for large projects where consistency is important.
I am not seeing that. I have a few AI-assisted projects using tailwind and scrolling through it now 99% of it looks... completely modern and professional. I had previously asked it to "completely refactor, a rewrite if needed, all the tailwind/css/app styles. ensure visual and code consistency across pages".
Modern coding tools add tons of their own content, but none of the above was "a lot of context engineering".
Earlier quoted context omitted.
If you want a bunch of tailwind class slop, then yes. Otherwise, A lot of context engineering is needed if you want it to write modular tailwind components properly for large projects where consistency is important.
Absolutely, but the AI era seems to have lowered the bar for what's considered passable code. Slop works for most projects.
Very sad to hear, I bought Tailwind UI years ago and although it was a lot more expensive than I wanted, I've appreciated the care and precision and highly recommend buying it (It's now called Tailwind Plus) even still (maybe even especially now). Mad props to Adam for his honesty and transparency. Adam if you're reading, just know that the voices criticizing you are not the only voices out there. Thanks for all you'…
What most don’t realize is that this will happen to most businesses in all categories as more people rely on ChatGPT and Claude for discovery. No discovery - no business. And same with ads.if OpenAI decides not to add ads - prepare for even faster business consolidation. Those businesses preferred by llms will exponentially grow, others will quickly go out of business
What about restaurants, transportation, construction, healthcare, or manufacturing?
Will those go out of business too?
Something’s wrong when a key piece of foundational web tech is staring down unsustainability. Tailwind is almost ubiquitous these days. It needs to continue to exist. Small businesses being eaten by AI is a net negative, because they’re in a unique position whereby they need to actually have to listen to customers vs just optimizing for a rando middle manger’s promotion in BigTech.
You could go back in time and say this about jQuery. Tailwind's future was always questionable because CSS is growing in new and amazing ways, and wrapping the complexity of new CSS features into helper classes isn't really a sustainable model. That said if someone wants a business model, figure out a way to get paid to get AI to make UIs using newer CSS features, because right now it's quite terrible at it.
There were originally snippets but it’s not reusable in a proper sense based on components like a design system. Each snippet may have overlaps but you can’t get it together properly.
Next there was catalyst, a react component library but it was barebones and doesn’t tie into the snippets.
And then there were templates, which again is another direction.
It would have been better if it was thought out. Design system. Component library. Snippets built on a solid base.
The paid products Adam mentions are the pre-made components and templates, right? It seems like the bigger issue isn't reduced traffic but just that AI largely eliminates the need for such things. While I understand that this has been difficult for him and his company... hasn't it been obvious that this would be a major issue for years? I do worry about what this means for the future of open source software. We've lo…
Didn't he (half) jokingly ask Anthropic to buy Tailwind a few weeks ago, right when Bun was acquired? Makes a lot more sense now.
source?