Live data from Hacker News

Konsta UI – Mobile UI Components Built with TailwindCSS

konstaui.com

161–170 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#161

Earlier quoted context omitted.

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

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

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

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#162

Earlier quoted context omitted.

So have I. So now who's anecdotal evidence wins? It really is what it comes down to, isn't it?

This isn't about winning dude. Some people like Tailwind and find it incredibly helpful. Some people don't. Some people actively despise Tailwind. No one has to 'win'. All these opinions can coexist.

That was the point of my rhetorical question. When comparing anecdotes, no one "wins" because both are unprovable.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#163

Earlier quoted context omitted.

So have I. So now who's anecdotal evidence wins? It really is what it comes down to, isn't it?

I'm not the one arguing that a particular technique doesn't scale or that its advocates don't know what they're doing. Of course you can build big things with semantic CSS. You also can with Tailwind.

I'm sure they can in Tailwind, but it hasn't been my experience, and that's what I meant by my rhetorical question, anecdotal evidence doesn't really matter.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#164
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…

Tailwind classes map very directly onto CSS properties and those properties and their values for all tailwind classes are very prominently displayed in the Tailwind documentation. There are going to be some classes that do a bit more for you than set a property, but they're not the majority.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#165

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.

Tailwind only extends on CSS, so I fail to see how one can fail to understand CSS but like Tailwind.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#166

Earlier quoted context omitted.

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

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

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

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#167
post #165

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.

Tailwind only extends on CSS, so I fail to see how one can fail to understand CSS but like Tailwind.

Concepts like cascading aren't really present in Tailwind.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#168

Earlier quoted context omitted.

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

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

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

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#169

Earlier quoted context omitted.

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

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

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

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#170
post #130

Earlier quoted context omitted.

I have a really hard time seeing someone use Tailwind as a shortcut because they don't know CSS. That comment does not say what you think it is. They are not saying they use it because they don't know CSS. The maintenance is what makes Tailwind awesome. I've written CSS professionally since Internet Explorer 6 and have gone through many different strategies for writing maintainable CSS (BEM, OOCSS, SCSS and multiple…

Funny, to me arguing for Tailwind is like arguing for copy pasting code around instead of using functions and classes, which the Tailwind devs literally tell you to do by the way. I mean, when I saw their official recommendation for maintenance of code and reusing styles was to use multiple cursors , I had to laugh out loud. https://tailwindcss.com/docs/reusing-styles

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.

Post reply on HN