Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Konsta UI – Mobile UI Components Built with TailwindCSS

konstaui.com

Post reply on HN
Print view View original

221–230 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#221

Post by satvikpendem »

kaba0 wrote: post #219
satvikpendem wrote: post #39

Earlier quoted context omitted.

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 fir…

> 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.

On 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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#222

Post by kaba0 »

satvikpendem wrote: post #92
cageface wrote: post #89

Earlier quoted context omitted.

I’ve used Tailwind successfully on several large codebases. It’s the only approach to CSS I’ve used that didn’t make me hate styling HTML.

I've often found that people who are in the frontend don't properly learn CSS and just hack it together. That was me too for a long while which is why I hated it. Then I started learning it from first principles and it makes a lot of sense. Now I can build whatever I need in plain CSS classes.

CSS makes sense, but it will still f*ck up a completely different page than the one you are working on because that property you changed somehow got tangled with that shitty Angular stylesheet and it was only spotted in prod.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#223

Post by satvikpendem »

kaba0 wrote: post #220
satvikpendem wrote: post #61

Earlier quoted context omitted.

If 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

“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”.

Tailwind 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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#224

Post by kaba0 »

satvikpendem wrote: post #105
Kiro wrote: post #102

Earlier quoted context omitted.

Saying people use Tailwind because they don't know CSS well enough is simply untrue. I feel like you don't even want to understand why people actually like Tailwind. It's not like you arguing against it will make us stop using something we love.

Lots of examples of it online of people using Tailwind because they don't know CSS well enough, it's not even debatable when they themselves literally claim that's why they use it. Even in this thread there are people doing so: https://news.ycombinator.com/item?id=34921960 I understand perfectly well why people like Tailwind. The problem is not initial productivity; indeed, I can write bash scripts too very quickly t…

So you claim that CSS itself is easy to maintain? Because I very much disagree with that.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#225

Post by satvikpendem »

kaba0 wrote: post #222
satvikpendem wrote: post #92

Earlier quoted context omitted.

I've often found that people who are in the frontend don't properly learn CSS and just hack it together. That was me too for a long while which is why I hated it. Then I started learning it from first principles and it makes a lot of sense. Now I can build whatever I need in plain CSS classes.

CSS makes sense, but it will still f*ck up a completely different page than the one you are working on because that property you changed somehow got tangled with that shitty Angular stylesheet and it was only spotted in prod.

Again, only if you don't work with scoping. On any other React project, we do.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#226

Post by satvikpendem »

kaba0 wrote: post #224
satvikpendem wrote: post #105

Earlier quoted context omitted.

Lots of examples of it online of people using Tailwind because they don't know CSS well enough, it's not even debatable when they themselves literally claim that's why they use it. Even in this thread there are people doing so: https://news.ycombinator.com/item?id=34921960 I understand perfectly well why people like Tailwind. The problem is not initial productivity; indeed, I can write bash scripts too very quickly t…

So you claim that CSS itself is easy to maintain? Because I very much disagree with that.

It is, again, if it's scoped.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#227

Post by satvikpendem »

kaba0 wrote: post #217
satvikpendem wrote: post #95

Earlier quoted context omitted.

Once you know the syntax of CSS properties you can jump into any codebase and instantly know what’s going on. With Tailwind you’re forever jumping between components and figuring out what that one long line of class names is actually doing.

No, one is a restricted subset of the other, and that means you can better reason about a less expressive language. This is basically what you would have with a non-Turing complete language vs Turing complete one.

Subsets and DSLs can often be worse than the language they're supposed to replace, and moreover, you need to learn a new proprietary language on top of that. There is no need for me to write Tailwind classes when I can just write their equivalent properties in CSS instead.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#228

Post by kaba0 »

satvikpendem wrote: post #171
Kiro wrote: post #170

Earlier quoted context omitted.

The point is that I will never go back to not using syntax highlight, and I'm sure you understand that it would be futile trying to convince me otherwise. I wouldn't take anyone doing that seriously, and similarly I can't take you seriously. Yes, being able to copypaste self-contained HTML with all styling included and no depedencies is amazing.

That's nice for you. Similarly, I cannot take anything recommending copy pasting code seriously either, and I'm sure you understand that it would be futile trying to convince me otherwise. I wouldn't take anyone doing that seriously, and similarly I can't take you seriously.

Arguably, html+css is not code though.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#230

Post by satvikpendem »

kaba0 wrote: post #228
satvikpendem wrote: post #171

Earlier quoted context omitted.

That's nice for you. Similarly, I cannot take anything recommending copy pasting code seriously either, and I'm sure you understand that it would be futile trying to convince me otherwise. I wouldn't take anyone doing that seriously, and similarly I can't take you seriously.

Arguably, html+css is not code though.

Copy pasting text*, then.
Post reply on HN