4 ms·
The 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
by antihero 4y ago
The 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 agoI am being forced to use it if my employer does, don't I? I find it more interesting that people get upset whenever others mention the downsides of Tailwind.
- monkey_monkey 4y agoI guess if the other engineers around you have coalesced around using Tailwind you may need to reasses how you go about presenting your position as you clearly aren't having the impact you feel you should be.
- satvikpendem 4y agoNot all decisions are so easily reversed. We have started rewriting parts out of Tailwind but it was chosen initially because it seemed good. That doesn't mean the engineers today continue to want to use it, and indeed many don't, hence the rewrite.
- monkey_monkey 4y agoWell you should probably get on with that and then conduct a post-mortem to understand why your team's decision making process was so flawed. Also it's good to see that you're not in fact FORCED to use it, but can change and reconsider.
- satvikpendem 4y agoWhat a weird definition of force, but okay. It doesn't seem like you're interested in any negative criticism of Tailwind but yes we will have a post mortem.
- kaba0 4y ago“High-level languages at best repackage normal machine code instructions that when composed together act just like.. regular machine code. So there's literally no point in using them“ 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”.
- satvikpendem 4y agoTailwind vs regular CSS and assembly vs high level languages is a false comparison, sorry. The latter is a strict net benefit, the former is...not.