5 ms·
Using it wrong on every codebase that wasn't even made by me but instead by my employers? If it's happening that many times, the tool is to blame. More likely
by satvikpendem 4y ago
Using it wrong on every codebase that wasn't even made by me but instead by my employers? If it's happening that many times, the tool is to blame.
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.
- techpression 4y agoThen every conceivable tool is to blame, especially within computer science, they’re all definitely used wrong more often than not.
- satvikpendem 4y agoCorrect.
- mort96 4y agoWait are you now just conceding that your criticism of Tailwind has no merit and could be replaced by a generic "All software is bad" meme?
- satvikpendem 4y agoI am parodying the parent's broad over generalization of tools. Yes, by their logic, they would concede that all software is bad. That doesn't mean some tools aren't better or worse than others. Just because hammers have flaws doesn't mean I'd use a hammer to screw in a nail, even if some do.
- techpression 4y agoThat’s not what you said though, better or worse is just moving the goal posts, and it’s of course contextual and relative. And no, by my logic most software is bad, not all, and I would actually say that’s true.
- antihero 4y agoThe idea of approaches changing and becoming obsolete and having to be changed is a natural part of software. Shouldn’t stop innovation. TW works well for many experienced people who are very happy with it.
- satvikpendem 4y agoIf it's real innovation, like jQuery imperatoveness to React et Al's declarativeness, sure I'd agree with you. But Tailwind is simply not innovation, it's at best repackaging normal CSS properties that when composed together act just like...regular CSS classes. So there's literally no point in using them. For example: https://twitter.com/stolinski/status/1613699772111638530 https://twitter.com/stolinski/status/1613699772111638530
- NayamAmarshe 4y agoShould also read the reply then: https://twitter.com/adamwathan/status/1613718281969635328 https://twitter.com/adamwathan/status/1613718281969635328 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.
- satvikpendem 4y agoI read most of the replies to the tweet I linked, including Adam's. It's simply not compelling enough for me to use Tailwind.
- monkey_monkey 4y agoThen don't use it. I doubt that anyone is forcing you to. There are many alternatives. Move on, and stop getting upset with people who find it incredibly helpful.
- satvikpendem 4y ago
- zmxz 4y ago> Using it wrong on every codebase that wasn't even made by me but instead by my employers? If it's happening that many times, the tool is to blame. 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?
- satvikpendem 4y agoI assure you these aren't really small companies with no one knowledgeable about frontend coding standards. Insinuating that they're "using the tool wrong and therefore it doesn't work for them" doesn't do it any favors. If I see the same patterns everywhere and which even online people ran into the same troubles, I will blame the tool, absolutely. Tools are not dogmatic, they are meant for us to use. If we use them wrong, it is the tool that must change, not us. 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.
- zmxz 4y agoYou can assure me with the might of 1000 exploding suns, but it STILL means nothing. 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.
- jen20 4y ago> Using it wrong on every codebase that wasn't even made by me but instead by my employers? If it's happening that many times, the tool is to blame. You could say that about chainsaws lopping off arms. Perhaps the user is not sufficiently competent to use the tool correctly…
- satvikpendem 4y agoIf chainsaws are popping off arms, then maybe we should have safety features, you know, like many blade driven devices already do these days. Again an example of a tool that evolves to meet users' needs instead of resorting to "you're using it wrong," this is a basic principle of product design.
- kaba0 4y ago> Using it wrong on every codebase that wasn't even made by me but instead by my employers? If it's happening that many times, the tool is to blame 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.
- satvikpendem 4y agoOn other projects I use React with CSS Modules or CSS-in-TS so this whack-a-mole never happens to me since every class is local. If that's not your setup then sure Tailwind works fine (but it's probably still more maintainable to use CSS Modules at the very least) but if it is then it's much less ergonomic to use Tailwind.