Tailwind is made for a component world where reusability is at the template/component level. This also covers both scoping issue with css: the usual issues with the single global namespace for classes and the unlimited depth of the descendant selector. That is even with scoped classes if your app has component nesting as then a selector like .A_box::hover .A_btn will select the class A_btn both in and . Tailwind solu…
So do you do sibling selectors by using the array index in a `.map` call?
I suppose it depends if you're trying to build the perfect website, or just want to get something launched fast. I usually build websites to solve a problem, or to try out a business idea. The structure of the HTML and whether I am using a web framework are not important to me. The main thing is, can I get this finished and looking great in a few days.
I hear this argument a lot, on the surface it makes sense. We all want to ship fast. Right? But then... I try to imagine how Tailwind allows you to style your site in a few days, but it'd take you, the same person, what... weeks, to style it with CSS? It's so ridiculous it's making me laugh out loud just imagining this somehow. As if CSS is this thing for rocket engineers that is way beyond a common man's grasp? Seri…
What makes you think tailwind would be hell in the future though? It's just a load of classes on html elements. Maintenance is pretty easy. I do agree with you on the headline though, of course tailwind hasn't won anything!
First, the site uses some weasel language to speak about how much they're "focused on performance" in such a way as you think Tailwind is literally faster than doing normal CSS. It's not. It's a heavy approach and while you can always find edge cases to the contrary, in general it leads to pages that add lag and load to people's devices. If you have a very simple page this doesn't matter, but as your site/business gr…
Reading the bloated HTML when using Tailwind is less painful than dealing with all the cascading crap of CSS.
> And for those that prefer a different editor? A plugin is likely available for that, too. I use PHPStorm a lot; https://www.jetbrains.com/help/phpstorm/tailwind-css.html Panic's Nova? https://extensions.panic.com/extensions/jasonplatts/jasonpla... Vim? https://vimawesome.com/plugin/coc-tailwindcss etc.
If I made a hammer but you need a special glove to use it proficiently, then I didn’t make a very good hammer
As opposed to all those other programming languages/libraries/frameworks for which noone ever benefits by installing a plugin for their editor.
Missed the underlying point but I'll make it explicit - if a plugin is "needed" that is also a red flag for me.
I suspect the number of developers with zero plugins in their IDE of choice is vanishingly small. That said, it's not needed . It's just a quality-of-life improvement, like most other IDE features. You can write a Tailwind site in Notepad, if you prefer.
Oh for sure, and devs should do what is needed to be more efficient and to make their development enjoyable. The poster I was responding to said "you have to install the vscode plugin" to enjoy using Tailwinds. So that's the specific part I was responding to.
Kinda. If React dies I'll be sad. While most of React is BS, the "ReactDOM" component, the Virtual DOM model that is applied to the real DOM by "delta" diff, is a solid concept that deserved to live. Unfortunately we do tend to throw out the baby with the bathwater, when we decide something is uncool. We're a very stupid species.
When has anything in tech ever actually died? I guess there will be people building sites in React forever. Haha
I get the challenge of dead CSS, I think there are strategies for managing that in complex apps without "ditching" CSS. And my understanding of Tailwinds is that it starts to break down for larger/complex apps also (but I've only used it on smaller things personally so that's just based on things I've read). I never try to be dogmatic about new things - so I'd try it again. I just haven't seen the benefits yet myself…
> there are other strategies True, but those usually involve adding some sort of linter to ensure that your style sheets are clean, which is an additional build step, which is an opportunity for a build to fail. Tailwind gives me this out of the box and doesn’t require any sort of manual lifting because it does this automatically. > Tailwind starts to break down for larger/complex apps also This hasn’t been the case…
Thanks for the data point re: larger apps. Like I said, haven't had that experience with Tailwinds specifically so I can only go by the various things I read about those who have. I'm sure it's like any other tool - it can be used or abused.
> Being able to think "Hmmm, I want a rounded button, with a border and a blue background" I rarely think this. It's usually “I want a button that looks like all other buttons on my site”. Vanilla CSS is great for that.
Tailwind is also great for this. You create components with Tailwind that make this trivial
Yes, the biggest drawback of Tailwind is React. Or specifically, relying on components as the mechanism for style composition.
+1. Let's say things how they are: Tailwind is a small catastrophe from an implementation, performance and maintenance point of views. It got few things quite well in being a more modern bootstrap, had a stellar marketing and it's color palettes are really well done and leagues above the default material ones. ...that being said... Tailwind's biggest pro is that it allows people that _don't_ know css that much to sty…
>> Tailwind's biggest pro is that it allows people that _don't_ know css that much to style stuff more consistently and easily. But that's where it ends. I'm considering advocating for a move to TW at work. Most of the devs _don't_ know CSS well enough to style stuff consistently and easily. We have very complicated cascades, and sibling style imports, and "semantic" class names. Sure, maybe the answer is "level up y…
Try Tailwind. I was a complete hater before I sat down and committed to one week project with it and I am frankly ashamed at how off my assessment was prior to using it.
Gray beard's 5c: Tailwind is a farce and a catastrophe. It's as modern as the style parameter is, and it's as reusable as a moving a dirt pile from one corner to the next. You're not learning anything valuable by learning Tailwind. Learn CSS, that will stick with you for the next 20 years. It amuses me when a library is implemented 'with tailwind', which means it's totally useless to the people _not using tailwind_,…
I’ve learned CSS, used Bootstrap, and tried a bunch of other tools. Tailwind ecosystem is the fast approach to building web UIs in my experience. It doesn’t matter if you know CSS or not. Nobody gains if you know CSS per se. People gain when you deliver finished projects. Tailwind helps ship projects faster.
Developers gain if they know CSS. Just like JavaScript - for either, if you understand the underlying base technology, it doesn't matter what framework you are presented with, you can learn the specifics of that framework fairly quickly, in my experience.