More likely that the people who use it and like it (for now) have never have to handle large amounts of components and refactoring them. It's basically impossible.
Trends come and go, who's to say that in a few years we decide, like jQuery, that hey, maybe this utility first approach isn't all that great? Yet at that point we'd have lots of legacy code to refactor, again just like jQuery.
There is no number here, you are basing this on your own experience and without any statistical analysis. Also no one really knows whether you or people you work with are genuinely trained and able to use the tools and/or program in a scalable, maintainable way.
Therefore, what you wrote is just a biased opinion based on a tiny, negligible amount of user(s).
Not taking into account opinions of other devs here, who claim the tool really helped them, turns this into a multiplayer monologue. You're adamant the tool is to blame and you found what works for you. Why continue to comment on Tailwind and not on the tool that's posted for discussion? Can you articulate what kind of win you expect here?
The tool posted for discussion prominently displays its usage of Tailwind, so why wouldn't I comment on it? Must I only comment on the tool itself without anything in its periphery? We see a lot of people on HN comment on a Rust based tool too, it's not uncommon. You are free to comment on it or something else as you please too.
I'm not insinuating that those unknown entities that only you know of are using the tool wrong. I'm literally claiming that they are because being "not really small company" says absolutely nothing about the way their engineers do their job.
> If I see the same patterns everywhere
"everywhere" is, again, something that exists in your head only and no one else knows what "everywhere" is. Where is everywhere? Who exactly are the people who are running into these unknown troubles? Are they knowledgeable engineers? Do they understand underlying problem that the tool solves? I'd say that you are consuming resources which gather people who run into problems due to their lack of knowledge, such as stackoverflow.com so yes, the pattern you'll see is problems.
> I will blame the tool, absolutely
Because the tool needs to bridge the gap between what people understand and what they want to achieve, there's literally no responsibility on the human in this story. Great thinking, let's see how that plays out :)
> If we use them wrong, it is the tool that must change, not us.
If you want to achieve the goal, the easiest thing to change is you and not the world around you. But by all means, you do you, the only currency you'll effectively pay with is your invaluable and irreplaceable time.
> Must I only comment on the tool itself without anything in its periphery?
I didn't tell you what you *must*, I asked why you didn't. You still have the option to do so, but that would require that you actually invest time into checking out Konsta UI - which you didn't, right? Is my assumption correct? You just didn't do it but you commented on what you disliked. I think that's all there is to it.
Self-proclaimed professional like you should not skim text. You miss the point that way.
> I'd say that you are consuming resources which gather people who run into problems due to their lack of knowledge, such as stackoverflow.com so yes, the pattern you'll see is problems.
Whatever numbers I give you will be unconvincing to you, is what I meant. So why should I try to convince you, when you yourself also pull No True Scotsman if I tell you I worked with good engineers who knew what they were doing? You will just say I am "consuming the wrong resources." Anything I say will not convince you.
Therefore there is nothing I could say to convince you further.
Wait, are we talking about CSS? Because I have yet to see a big enough application where the CSS wasn’t some “whack-a-mole” game when you had to change something supposedly locally.
You could say that about chainsaws lopping off arms. Perhaps the user is not sufficiently competent to use the tool correctly…
For example: https://twitter.com/stolinski/status/1613699772111638530
The only people I know who dislike tailwind are those who either have never used it to make a project because of bias (hello past me) or those who dislike having faster development speed.
Tailwind objectively saves time, yes, objectively.
There are many alternatives. Move on, and stop getting upset with people who find it incredibly helpful.
Also it's good to see that you're not in fact FORCED to use it, but can change and reconsider.
Not having CSS inheritance anywhere already make it much much better. Sure, it is not novel, but it does fix many warts of “normal CSS”.