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

71–80 of 243 posts

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#71

Post by satvikpendem »

mort96 wrote: post #67
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.

Tailwind is under the MIT license. In what sense is it proprietary?

I should have meant proprietary as in non-standard, not non-open-source. By proprietary I meant that they wrote their own DSL and in the future if it needs to be ported over, it will be much harder. It's like CoffeeScript versus Javascript/TypeScript.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#72

Post by satvikpendem »

bobthepanda wrote: post #30
dmix wrote: post #25

Earlier quoted context omitted.

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

Css in JS (as in, inline styles) is just going to be a lot worse than class names because JS is fundamentally performance bottlenecked way harder than CSS is.

I'm not sure I understand what you mean by CSS in JS, since you say inline styles next. Are you talking about JSX having a style component? Or Tailwind within the className in JSX? Or CSS in JS libraries like styled-components?

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#73

Post by NayamAmarshe »

satvikpendem wrote: post #61
antihero wrote: post #59

Earlier quoted context omitted.

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.

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

Should also read the reply then: https://twitter.com/adamwathan/status/1613718281969635328

The only people I know who dislike tailwind are those who either have never used it to make a project because of bias (hello past me) or those who dislike having faster development speed.

Tailwind objectively saves time, yes, objectively.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#74

Post by mort96 »

satvikpendem wrote: post #71
mort96 wrote: post #67

Earlier quoted context omitted.

Tailwind is under the MIT license. In what sense is it proprietary?

I should have meant proprietary as in non-standard, not non-open-source. By proprietary I meant that they wrote their own DSL and in the future if it needs to be ported over, it will be much harder. It's like CoffeeScript versus Javascript/TypeScript.

So it's a criticism which applies to literally every use of some library or framework to make writing web apps easier.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#75

Post by mcluck »

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

You can write CSS-in-JS style without a runtime https://vanilla-extract.style/

In my opinion, this gives you all of the supposed benefits of Tailwind without all of the noise and annoying opinions that come with Tailwind

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#76

Post by gimliapp »

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.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#77

Post by bobthepanda »

satvikpendem wrote: post #72
bobthepanda wrote: post #30

Earlier quoted context omitted.

Css in JS (as in, inline styles) is just going to be a lot worse than class names because JS is fundamentally performance bottlenecked way harder than CSS is.

I'm not sure I understand what you mean by CSS in JS, since you say inline styles next. Are you talking about JSX having a style component? Or Tailwind within the className in JSX? Or CSS in JS libraries like styled-components?

Styled-component also has this issue but mostly I mean literally assigning a string to the html attribute style.

Classname strings are fine.

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#78

Post by zmxz »

satvikpendem wrote: post #34

What is it about everyone using Tailwind? It inevitably becomes a mess in every codebase I've used it in; it's like Perl, a write only language. I just use Vanilla Extract (with their Sprinkles API) and call it a day, it uses TypeScript as the preprocessor language and then compiles it to raw CSS, similar to SCSS but without writing SCSS. https://vanilla-extract.style

It doesn't become a mess, but it's interesting you chose to comment on Tailwind and not KonstaUI despite topic being KonstaUI. Do you have any opinion to share on KonstaUI or any other helpful insight, except giving yourself credit for what you use and being negative towards the rest?

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#79

Post by zmxz »

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…

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

There is no number here, you are basing this on your own experience and without any statistical analysis. Also no one really knows whether you or people you work with are genuinely trained and able to use the tools and/or program in a scalable, maintainable way.

Therefore, what you wrote is just a biased opinion based on a tiny, negligible amount of user(s).

Not taking into account opinions of other devs here, who claim the tool really helped them, turns this into a multiplayer monologue. You're adamant the tool is to blame and you found what works for you. Why continue to comment on Tailwind and not on the tool that's posted for discussion? Can you articulate what kind of win you expect here?

Re: Konsta UI – Mobile UI Components Built with TailwindCSS

#80

Post by kytazo »

On the tailwind argument I don't really feel like ever going back in spending a good 2 minutes coming up with a non conflicting yet descriptive class name only to end not using it at all cause I decided to implement the requirement in a different way. Not to mention the relief from the constant css/html context switch you undergo indefinitely.

I can't really comment on how it scales in big projects tho.

Post reply on HN