Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tailwind UI

tailwindui.com

Post reply on HN
Print view View original

361–367 of 367 posts

Re: Tailwind UI

#361

Post by thrownaway954 »

thrownaway954 wrote: post #341
thrownaway954 wrote: post #340

Earlier quoted context omitted.

i think you're missing the point. extracting "component" as code snippets does nothing if one day your boss tells you to change all the size and colors of all the buttons. you still have to go through your entire site and make the changes manually at every instance... or have the foresight to have a class on every button that you can reference through pure css to make the change without breaking tailwind... but at th…

well... looking at the @apply directive that they have, i think found the answer to this. i've been proven wrong: https://tailwindcss.com/course/composing-utilities-with-appl...

continuing to fall on my sword from yesterday... my god... i am impressed. i've been going through the screencasts they have and i think i'm going to ditch bootstrap and use tailwind for my next project.

https://tailwindcss.com/screencasts/

Re: Tailwind UI

#362

Post by rhizome »

jacobsenscott wrote: post #230
rado wrote: post #4

Earlier quoted context omitted.

Looks good and polished, but that landing page requires 165 KB of CSS, gzipped. That's, to put it lightly, ridiculous.

Congratulations on building your time machine. And welcome to 2020. 165kb is nothing these days and only takes a fraction of a second to download and processes even on a slow computer. You're going to find all kinds of other cool cool stuff you didn't have in the 90's. Did you know you can build and deploy an entire application without ever running a compiler or touching a physical machine now? We have REPLs were you…

>Did you know you can build and deploy an entire application without ever running a compiler or touching a physical machine now? We have REPLs were you can interact with your application live, in real time.

How do I interact with REPLs in real time without touching a physical machine?

Re: Tailwind UI

#363

Post by hackerman555 »

I like the design, hate the implementation.

Really doesn't work with react.

react + styled components is god mode. This is a step down (aside from the design).

At the end of the day, CSS isn't that hard anymore.

Design it in figma. Put it into zeplin. Copy paste the styles into a styled-component. You're done.

tailwind is only a step up if you're a russian php developer who has been using bootstrap for the last 10 years.

Re: Tailwind UI

#364

Post by hackerman555 »

rjknight wrote: post #37
efdee wrote: post #33

Judging from all the positive comments in this thread, clearly I must be missing something. This looks horrible to me. Instead of meaningful CSS classes you just get a bunch of small classes that do very small things, which you're supposed to combine until it looks like what you want. How is that better than writing your CSS manually? (Again, I realise the failure is probably on me. But I don't get it.)

There are some nice aspects: - The classes cover many common use-cases and, in some cases, present a simpler "API" than hand-rolled CSS would - You can eyeball a HTML fragment and get a good idea of how the pieces fit together, compared to the normal approach of needing to work out what each individual class does, and then how they fit together. It's easy to remember what the Tailwind classes are doing. - It's dumb,…

> It's dumb, but the ability copy-and-paste entire HTML fragments from one place to another and have the styling "just work" is slightly mind-blowing

Not really. styled-components makes this simple if you're using react.

Re: Tailwind UI

#365

Post by jhardy54 »

dwild wrote: post #350
jhardy54 wrote: post #264

Earlier quoted context omitted.

In that case, isn't that basically style="color: var(--gray-500);" with extra steps? I love to see people experiment for the sake of experimentation, but I'd be hesitant to adopt Tailwind as an engineer unless I understood why they weren't just CSS variables.

CSS variables are still relatively new though, unsupported until about March 2018 in all browsers, yet the first commit over TailwindCSS is from Jul 20, 2017, nearly a year before browsers even supported the feature. Even today it seems like 11% of users doesn't have support for variables. Could make sense to add support for variables now, but for the sake of backward compatibility, it does make sense to keep it with…

My point isn't that Tailwind should've used CSS variables in 2017, it's that technology from 2017 isn't very compelling in 2020.

> I love though that as an engineer you would be hesitant to use Tailwind, but you are not aware of how new variables are.

Why would you think I'm unaware? Please see: https://caniuse.com/#feat=css-variables

I'm not writing software for IE 11 (released in 2013), Opera Mini, QQ, or Baidu, so CSS variables are widely supported for my target demographic.

Re: Tailwind UI

#366

Post by tpetry »

porker wrote: post #318
tobr wrote: post #108

Earlier quoted context omitted.

It might happen, but I don’t think it would kill the value. There are tons of free and pretty great UI kits, CSS themes, etc already. Adam Wathan has done a really good job building up a community around Tailwind, and that brand and goodwill is part of the value here, I think.

> There are tons of free and pretty great UI kits, CSS themes, etc already. There are tons that look visually appealing, but very few I've found that take a component-based approach (where they document each component individually - or think about how they interplay with each other). I've found the CSS is usually muddled, they often have legacy build pipelines that has to be rewritten to fit with Webpack, and a disti…

You just can take any bootstrap theme. The component design is the basis of bootstrap.

Re: Tailwind UI

#367

Post by alharith »

tasogare wrote: post #154
alharith wrote: post #137

Earlier quoted context omitted.

> The problem with this IMO is that some enterprising person will just use regular tailwind (or another utility-css framework like tachyons) and re-implement all of these components and give it out for free, circumventing the license and killing the value of this. No because I believe that for every enterprising person wanting to circumvent paying for software, there are that many people who want to support the entre…

I wouldn’t bet on that. Most people want things for free and would stole digitized assets if they can go away. In a way what you wrote is true, but I’ll reverse it: for anyone willing to pay, there are many...

Following up on this, it seems like they did quite well.
Post reply on HN