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

131–140 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#131

Post by satvikpendem »

twism wrote: post #120
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…

Just not possible to use tailwind without a really good grasp of css

¯\_(ツ)_/¯ Take it up with them, I'm not the one saying it's easier than learning CSS.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#132

Post by omnimus »

satvikpendem wrote: post #119
phphphphp wrote: post #115

Earlier quoted context omitted.

I’ve recently started working on 2 legacy codebases, one with tailwind and one with scss. The #1 problem — that has cost me multiple hours! — is inheritance, because how developers write CSS and how business people think about design are very different. I constantly find myself causing side effects when making any change to the css, it’s a headache. I don’t think tailwind is perfect but coming into a well-established…

I work in React so all of our CSS is scoped, at the very least with CSS modules, so we never get to a point where we have global CSS, at all. If you're working on a project that uses global styles, then yes, it will be extremely painful. But in the days of components, Tailwind simply is worse to me from a maintainability perspective than just having scoped CSS. It is at best equal to CSS classes because inevitably th…

And many people don't work in components or scoped CSS. Utility classes help so much in those cases.

The only problem with tailwind is it goes super overboard with the idea. You want to use probably 30% of tailwind and use their naming convention. But once people start to write some long on demand single classes its always better just name a class and use CSS.

I think its because the authors need to be seem they are making updates all the time and can't accept that it's pretty much finished project. They also don't want to accept that utility classes are not solution to everything and good old CSS still has lots of use.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#133

Post by esperent »

wheresmycraisin wrote: post #70

Isn't making a component library antithetical to the way Tailwind is meant to be used?

Not in the slightest, tailwind even have their own UI library. Theirs is unstyled but there's nothing wrong with creating one with default styles.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#134

Post by s1k3s »

hobo_mark wrote: post #128
s1k3s wrote: post #111

Hey SaaS'ers, this is how you showcase a product.

What product though? There is nothing for sale.

Sorry, I was just praising the way it's presented because it has a demo right in your face, as opposed to the usual product landing pages.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#135

Post by NayamAmarshe »

satvikpendem wrote: post #117
NayamAmarshe wrote: post #113

Earlier quoted context omitted.

> Just because they say it's better doesn't make it actually better. They didn't say it's better. They said go ahead and use it first, before pulling out opinions. I perfectly understand your position, I've been there too but it's a complete 180 experience after you build just 1 project with it. It's a "won't go back" experience.

I think you missed my previous comments saying how I've used it extensively the past few years for employers. It's like a bell curve, you like it and think, wow, this is amazing. Then as the years pass and you start having to maintain it, you steadily dislike it until you get to not wanting to use it anymore at all. The people who currently like Tailwind might simply not have gotten to this later stage yet.

> Then as the years pass and you start having to maintain it, you steadily dislike it

> The people who currently like Tailwind might simply not have gotten to this later stage yet.

And yet somehow the projects you were assigned did? I don't mean any disrespect, but I find it a bit questionable that any big project that uses Tailwind has had maintainability issues when Tailwind itself is pretty new to the scene.

It'd be hard for you to prove this to be honest, while on the other hand, I could give you hundreds of thousands of testimonials countering your argument.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#136

Post by satvikpendem »

Kiro wrote: post #130
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…

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

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#137

Post by Kiro »

nicoburns wrote: post #125
Kiro wrote: post #98

Earlier quoted context omitted.

What you describe is not representative of how CSS is maintained in most companies. You always end up in a situation where it's impossible to track down what styles affect what elements so you start overriding and duplicating because you're afraid to touch existing CSS.

How can it ever be impossible to track down styles? The browser dev tools will tel you exactly which styles apply to which element.

Nothing is impossible but it becomes hard because the element is styled through multiple cascades, and you need to track it down both ways. When changing a class or a style you need to know what elements that change affects, which will be hard to track down because of the same reasons.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#138

Post by NayamAmarshe »

satvikpendem wrote: post #127
NayamAmarshe wrote: post #112

Earlier quoted context omitted.

Well at least I won't have to have 2 split windows just to know what 'image-caption' is and the tailwind class you wrote, perfectly readable and understandable. If long class names aren't your thing, then sure, use CSS, but I'd rather save time and have understandable code than maintain those CSS classes like "image-caption".

If you're writing only once, sure, have as long class names as you want, since you yourself don't want to maintain your code in the future apparently.

> since you yourself don't want to maintain your code in the future apparently.

Well, I don't appreciate the snarky comment, quite honestly. But okay, I'll assume you have had more experience than me, and you've managed things I haven't, have a good day.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#139

Post by satvikpendem »

omnimus wrote: post #132
satvikpendem wrote: post #119

Earlier quoted context omitted.

I work in React so all of our CSS is scoped, at the very least with CSS modules, so we never get to a point where we have global CSS, at all. If you're working on a project that uses global styles, then yes, it will be extremely painful. But in the days of components, Tailwind simply is worse to me from a maintainability perspective than just having scoped CSS. It is at best equal to CSS classes because inevitably th…

And many people don't work in components or scoped CSS. Utility classes help so much in those cases. The only problem with tailwind is it goes super overboard with the idea. You want to use probably 30% of tailwind and use their naming convention. But once people start to write some long on demand single classes its always better just name a class and use CSS. I think its because the authors need to be seem they are…

Sure, I agree with you there.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#140

Post by satvikpendem »

NayamAmarshe wrote: post #135
satvikpendem wrote: post #117

Earlier quoted context omitted.

I think you missed my previous comments saying how I've used it extensively the past few years for employers. It's like a bell curve, you like it and think, wow, this is amazing. Then as the years pass and you start having to maintain it, you steadily dislike it until you get to not wanting to use it anymore at all. The people who currently like Tailwind might simply not have gotten to this later stage yet.

> Then as the years pass and you start having to maintain it, you steadily dislike it > The people who currently like Tailwind might simply not have gotten to this later stage yet. And yet somehow the projects you were assigned did? I don't mean any disrespect, but I find it a bit questionable that any big project that uses Tailwind has had maintainability issues when Tailwind itself is pretty new to the scene. It'd…

Hundreds of thousands of testimonials from companies using it in production and had been for the past few years and as not a new project? Sure, send me a list. I expect to see all of the hundreds of thousands of them on the list. My email is in my profile.

It's anecdotal experiences at this point. As I said, I was using Tailwind from the beginning and loved it at first. Then the problems started.

Post reply on HN