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

101–110 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#101

Post by NayamAmarshe »

notpushkin wrote: post #97
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.

Yeah, Tailwind feels like Bash for CSS: save a few keystrokes here and there, at the cost of readability. The problem is, everybody already knows Bash. Tailwind? Not so much.

> everybody already knows Bash

Highly doubt it.

> at the cost of readability.

You mean the readability of "p-2 bg-red-500 text-lg font-medium" or "i-dont-remember-what-this-class-does"?

I'd argue the readability in Tailwind is better. Tailwind is highly indicative of what it does and doesn't waste time when it comes to consistency.

The only real argument is that it adds extra length to the class attribute, but then again, it doesn't cause issues like finding the same class in 50 different CSS files or not having any auto-completion.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#102

Post by Kiro »

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.

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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#103

Post by NayamAmarshe »

satvikpendem wrote: post #60
antihero wrote: post #57

Earlier quoted context omitted.

And your Typescript CSS in JS thing using some new thing? TW is at least well documented and widely used and based on a fairly formalised bunch of classes that builds upon a concept that’s been used for 10+ years.

It's not my thing, I didn't make it, for one. Then just use CSS at that point, it's been here 20+ years then. I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.

> I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.

Could just read the docs. https://tailwindcss.com/docs/utility-first

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#104

Post by bavila »

NayamAmarshe wrote: post #101
notpushkin wrote: post #97

Earlier quoted context omitted.

Yeah, Tailwind feels like Bash for CSS: save a few keystrokes here and there, at the cost of readability. The problem is, everybody already knows Bash. Tailwind? Not so much.

> everybody already knows Bash Highly doubt it. > at the cost of readability. You mean the readability of "p-2 bg-red-500 text-lg font-medium" or "i-dont-remember-what-this-class-does"? I'd argue the readability in Tailwind is better. Tailwind is highly indicative of what it does and doesn't waste time when it comes to consistency. The only real argument is that it adds extra length to the class attribute, but then a…

> You mean the readability of "p-2 bg-red-500 text-lg font-medium" or "i-dont-remember-what-this-class-does"

No, I'm pretty sure he means the readability of "absolute bottom-0 text-sm md:text-base text-white leading-relaxed tracking-tighter transition-all duration-300 ease-in-out m-3 md:m-4 px-6 md:px-8 py-4 md:py-6 opacity-0 w-full", as opposed to a single well-named class such as "image-caption".

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#105

Post by satvikpendem »

Kiro wrote: post #102
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.

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 that make me feel infinitely productive. It's what comes afterwards, the maintenance, the teasing of code written, that Tailwind makes so difficult.

And sure, use what you want, but I won't use it.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#106

Post by satvikpendem »

NayamAmarshe wrote: post #103
satvikpendem wrote: post #60

Earlier quoted context omitted.

It's not my thing, I didn't make it, for one. Then just use CSS at that point, it's been here 20+ years then. I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway.

> I simply don't understand how it can be superior to regular CSS in any way simply because it maps one to one onto CSS properties anyway. Could just read the docs. https://tailwindcss.com/docs/utility-first

I did, I even read Adam's initial post here on Hacker News itself. Just because they say it's better doesn't make it actually better. Indeed, to me, it is strictly worse.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#107

Post by szundi »

gimliapp wrote: post #76
fleetfox wrote: post #5

I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js

As much as I like Tailwind, I too does not understand the Tailwind-in-js thing for basic components likes buttons or checkboxes. Why not just create a button component in whatever framework you are using with scoped styles. This just seems like unnecessary coupling to me.

Because this is extra work?

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#109

Post by conradfr »

dmix wrote: post #25
fleetfox wrote: post #5

I'm trying not to be a hater but really how is this: https://github.com/konstaui/konsta/blob/master/src/shared/cl... better than css or even css in js

This is just unfamiliarity IMO. This is a component you reuse across tons of sites, it's not a one off component you're building for yourself. It's also not just a CSS framework like Bootstrap. This is full CSS + JS component's with functionality, Vue/React/Svelte framework integration, and events built in. Whether css-in-JS as a whole makes sense beyond these generic component type systems is a good question. There'…

Bootstrap has JS components.

And utility classes.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#110

Post by conradfr »

WA wrote: post #12

I’m using Ionic heavily and judge it through this lens. - The components for iOS look nice, but some things are off: Sheet modal is weird. Animation of modals or side panels feel too slow. - There are no animations when navigating forward or backwards. - The demo has scrolling issues on iOS Safari and doesn’t always show the header. - Unfaithful communication: it claims to give you native look and feel, which can nev…

Yes I'm impressed by their extensive documentation and the Ionic integration seems well thought out but it's not clear to me why I would use that instead of the integrated Ionic components that looks almost identical to this library.
Post reply on HN