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

51–60 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#51

Post by satvikpendem »

antihero wrote: post #48
satvikpendem wrote: post #38

Earlier quoted context omitted.

I see the Tailwind fans come out on any criticism of their library. I posted my comment a few minutes ago and already got a few combative comments almost immediately afterwards.

Yeah because you’ve jumped in on the attack on a post about something built with a tool that clearly gives a lot of people joy, in order to hawk your own thing. Getting whiny about people defending their own thing in response is kind of disingenuous. People got tired of vue people continuously doing the same thing about anything vaguely related to react, too.

No, what I'm actually getting tired of is people getting on the hip new proprietary but trendy JS/CSS thing like Tailwind and leaving other devs to clean it up in a few years.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#52

Post by nailer »

diceduckmonk wrote: post #9
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

If you compare a given snapshot of code containing utility css vs well defined CSS, then yes, it looks worst. The reality is that if the codebase and style code is in flux, that idealized CSS stylesheet will churn towards a being a mess of tech debt. Utility CSS contain redundancies (on the HTML side of things), but the rule of dumb is that you shouldn't refactor redundancies until you are absolutely sure what the un…

> The reality is that if the codebase and style code is in flux, that idealized CSS stylesheet will churn towards a being a mess of tech debt.

Interesting. That’s not been my experience. People tend to clean up as they go, eg if the design says we now need a thinner padding / gaps or a different colour blue, we change the variable, and if we spot cut and pastes we fix them.

It’s certainly much easier to refactor than visual classes mixed into HTML.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#53

Post by nailer »

o_m wrote: post #40
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

Tailwind (CSS) doesn't need a javascript runtime, the browser can run it natively

Tailwind is literally someone else’s PostCSS output.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#54

Post by antihero »

mulhoon wrote: post #31

These kind of libraries are always easy to spot in the wild because of their transitions on things like modals and action sheets don’t match native. They’re just not as smooth.

What exactly is a native mobile modal?

That said I’m inclined to agree - emulating system controls with CSS always feels very uncanny valley to me.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#55

Post by antihero »

satvikpendem wrote: post #49
antihero wrote: post #44

Earlier quoted context omitted.

I’ve found what you said to be completely untrue unless you’re totally lazy. If you’re building up a bunch of components, the tailwind classes are mainly within the basic components. In the first example of vanilla extract, it uses exact px measurements which already demonstrates it’s not geared to solve one of the primary selling points of tailwind (using config as a constraint to reduce mental overhead when buildin…

And have you had to work on hundreds of components that you had to refactor before? It's a write only language. > I’ve found what you said to be completely untrue unless you’re totally lazy. Ah yes, the laziness argument. Let's not blame our tools but ourselves for the tools are always good and righteous. If only those darn C programmers weren't so lazy writing their memory leaks.

I have, yes. It’s fine and no more annoying than css, styled or whatever else. If anything it’s easier because there’s consistent and constrained bunch of classes you can use.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#56

Post by throwaway29495 »

nailer wrote: post #53
o_m wrote: post #40

Earlier quoted context omitted.

Tailwind (CSS) doesn't need a javascript runtime, the browser can run it natively

Tailwind is literally someone else’s PostCSS output.

No, it's your own PostCSS output. At least if you want to only have the definitions you actually use.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#57

Post by antihero »

satvikpendem wrote: post #51
antihero wrote: post #48

Earlier quoted context omitted.

Yeah because you’ve jumped in on the attack on a post about something built with a tool that clearly gives a lot of people joy, in order to hawk your own thing. Getting whiny about people defending their own thing in response is kind of disingenuous. People got tired of vue people continuously doing the same thing about anything vaguely related to react, too.

No, what I'm actually getting tired of is people getting on the hip new proprietary but trendy JS/CSS thing like Tailwind and leaving other devs to clean it up in a few years.

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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#58

Post by satvikpendem »

antihero wrote: post #55
satvikpendem wrote: post #49

Earlier quoted context omitted.

And have you had to work on hundreds of components that you had to refactor before? It's a write only language. > I’ve found what you said to be completely untrue unless you’re totally lazy. Ah yes, the laziness argument. Let's not blame our tools but ourselves for the tools are always good and righteous. If only those darn C programmers weren't so lazy writing their memory leaks.

I have, yes. It’s fine and no more annoying than css, styled or whatever else. If anything it’s easier because there’s consistent and constrained bunch of classes you can use.

Then just use CSS at that point, since the classes literally just map onto CSS properties anyway (and sometimes not even, since they have to spend time to make new, or even older, rules work). That's what I don't get about Tailwind, at its best it's as good as CSS, but oftentimes stuff like SCSS, CSS-in-TS etc are simply better.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#59

Post by antihero »

satvikpendem wrote: post #39
NayamAmarshe wrote: post #37

Earlier quoted context omitted.

[flagged]

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…

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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#60

Post by satvikpendem »

antihero wrote: post #57
satvikpendem wrote: post #51

Earlier quoted context omitted.

No, what I'm actually getting tired of is people getting on the hip new proprietary but trendy JS/CSS thing like Tailwind and leaving other devs to clean it up in a few years.

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.

Post reply on HN