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

61–70 of 367 posts

Re: Tailwind UI

#61

Post by cageface »

saagarjha wrote: post #46
aosaigh wrote: post #40

Earlier quoted context omitted.

The same comment is at the top of every post related to Tailwind. Read this section in the docs and try it out before judging: https://tailwindcss.com/docs/utility-first The core principle is that you wrap up all UI elements into components. Most frontend and backend/template frameworks allow you to do this. You then verbosely apply the Tailwind classnames to perform styling, staying out of custom .css files all toge…

This just seems like inline CSS with less verbosity. Where’s the semantic meaning?

In my experience trying to do semantic CSS just adds a lot of extra cognitive overhead and breaks down in the inevitable requirements churn every project goes through.

I was skeptical of Tailwind too until I actually tried it. It’s one of those things like JSX that defies received wisdom but in real use is very nice.

Re: Tailwind UI

#62

Post by 6510 »

juretriglav wrote: post #2

I've been following this closely. Given the preview with some components listed it seems exceptionally well made: https://tailwindui.com/components There are also live demos of the app and marketing pages: 1. https://tailwindui.com/page-examples/landing-page-01 2. https://tailwindui.com/page-examples/detail-view-01# Plus a screencast on how to use it to build these pages: https://vimeo.com/393580241/82c6d7c5f6

Re: Tailwind UI

#63

Post by iudqnolq »

nickjj wrote: post #59
iudqnolq wrote: post #48

Earlier quoted context omitted.

They've implemented that, and have size sliders for some of the components. I presume the others are images so it's harder to steal the styling.

> They've implemented that, and have size sliders for some of the components. It seems they've only done it for the ones they are ok with making freely available. But that still leaves a vast majority of the components (almost all of them) as static images at 1 specific screen size. They should consider adding screenshots of each size, or a few second gif / video showing how it looks at various breakpoints. Otherwise…

I would like that. Personally I bookmarked this to come back to because so many of the components are listed as not yet implemented.

I do think they have a fourteen day free trial, though.

Re: Tailwind UI

#64

Post by fraktl »

It's great there's yet another UI framework on its way. Choice is awesome.

I'm a frontend guy (among other things) and for past 2 years I've been using Nuxt (app server, node.js) and Vuetify (material UI framework for Vue.js). Given what kind of results that stack can (and does) achieve, I wonder if people in the same boat as me (using the same stack) would even attempt to use Tailwind CSS/UI.

Whatever the case is, I'm glad there's a project that's useful and that helps authors finance their effort. Thumbs up!

Re: Tailwind UI

#65

Post by have_faith »

rjknight wrote: post #41
pcurve wrote: post #36

On the surface, the markup is pretty damn awful. But if you reach certain level of proficiency, this will definitely speed up development. Back End Developer Personally I would prefer Bootstrap over this approach.

I find that the verbosity is annoying at first, but it makes it incredibly easy to come back to some old HTML and work out exactly what it's doing, and why. Even with Bootstrap, you need to maintain a mental model of what the classes are doing and how they compose, and each custom class adds more complexity to that mental model. Yes, Tailwind has lots of classes, but each class does one thing , so reasoning about the…

> Tailwind has lots of classes, but each class does one thing

I think this masks a lot of complexity that you have to manage when taking on this approach. And it's not because the approach is good or bad, more what it is or isn't suited for.

The example on the homepage is very slickly presented, but the end result markup is extremely verbose. If I have a Card component, I would like to update them all at once when needed which is what css classes are generally good for. I find BEM naming conventions much more friendly to come back to than markup full of miniature class names.

Re: Tailwind UI

#66

Post by ahuth »

pcurve wrote: post #36

On the surface, the markup is pretty damn awful. But if you reach certain level of proficiency, this will definitely speed up development. Back End Developer Personally I would prefer Bootstrap over this approach.

That's fair. However, it is pretty straightforward to extract these to something reusable using Sass, css-modules, or templating (Handlebars, Nunjucks, React, etc).

So you can move really fast and experiment when you need to, and then extract to something shared when you're ready to DRY it up.

Re: Tailwind UI

#67

Post by wltprgm »

pcurve wrote: post #36

On the surface, the markup is pretty damn awful. But if you reach certain level of proficiency, this will definitely speed up development. Back End Developer Personally I would prefer Bootstrap over this approach.

The classes are exactly why it shines

Re: Tailwind UI

#68

Post by have_faith »

mattferderer wrote: post #20
chrshawkes wrote: post #9

Earlier quoted context omitted.

I'm tired of excuses for inferior tooling. If you truly know CSS, Tailwind is a waste of time.

Quite the opposite. It's a nice set of CSS variables. It still relies on much more CSS knowledge than a framework like Bootstrap. CSS frameworks are great because there is a flavor that should fit just about anyone.

It seems to require so much CSS knowledge that you might as well just use regular class names and write the CSS components yourself as it requires you to understand how flexbox etc works anyway to use it's utility classes properly.

Re: Tailwind UI

#69

Post by dinkleberg »

sandGorgon wrote: post #53

so the problem is that this is priced too high. Its not about free, but the real pricing market now is themeforest. For example - http://landrick.react.themesbrand.com/ is 17$. https://g-axon.com/wieldy-ant-design-react-redux-admin-templ... is 24$ (which uses ant design)

Tailwind UI is not a theme, it's a component library. The target audience is different.

I bought this the moment I got the email about it this morning because this is going to help my productivity in building web applications. When you use Tailwind, you aren't using a pre-made theme as you would with a bootstrap theme you buy, you are designing it from scratch.

With this UI kit you'll get some nice building blocks to become even more productive, but you'll still end up modifying stuff to make it yours.

Re: Tailwind UI

#70

Post by ecmascript »

Looks sexy but damn that's expensive. $250 for some pre-built styles I probably need to edit a lot anyway.

I rather use a free option like https://semantic-ui.com/ than pay that much. Maybe if you are company but it doesn't really work if you are a solo dev or using it for a side project.

Post reply on HN