Tailwind CSS v3.0 • Hacker News Board

Re: Tailwind CSS v3.0

#11

Post by ipaddr » Thu, Dec 09, 2021, 7:17 PM UTC

I just started using tailwinds. I found the daisyui plug-in to simplify the classes required and they add in the missing components.

Re: Tailwind CSS v3.0

#12

Post by yurishimo » Thu, Dec 09, 2021, 7:17 PM UTC

asimpletune wrote: post #3

Is there a link showing the delta between v2 and v3?

Here is the Upgrade Guide[0] and the Changelog[1]

0: https://tailwindcss.com/docs/upgrade-guide

1: https://github.com/tailwindlabs/tailwindcss/blob/master/CHAN...

Re: Tailwind CSS v3.0

#13

Post by yurishimo » Thu, Dec 09, 2021, 7:19 PM UTC

Really happy to see this before the end of the year. The JIT improvements and comprehensive arbitrary value support will no doubt come in handy for quick one-off projects or bespoke landing pages.

I'm happy they have also expounded upon some of the more common FAQs on the homepage, including the extraction to components.

Re: Tailwind CSS v3.0

#14

Post by gherkinnn » Thu, Dec 09, 2021, 7:19 PM UTC

awestroke wrote: post #6

Since I learned to write semantic class names, and to compose using scss or react components, Tailwind feels like it would be a big step back. I get that it would be kind of nice to prototype in, but is anybody here using it for complex apps or UIs?

It feels strange at first but then it's a bit like flying.

Re: Tailwind CSS v3.0

#15

Post by gunshowmo » Thu, Dec 09, 2021, 7:20 PM UTC

Looks fantastic. My only concern using this in a full React project is its lack of interoperability with standard libraries. It seems like for the best experience, you either buy Tailwind UI to use with a tailwind project for anything except the most basic UIs, reimplement the Tailwind UI components yourself, or have a weird mix of css-in-js and Tailwind CSS. Although I love the idea of HTML-native inputs all the way through, I tend to immediately run into issues where using a native interface instead of a JS-based implementation harms the user experience.

Props to the team though - I feel like this is something I'll try out for a marketing site.

Re: Tailwind CSS v3.0

#16

Post by [deleted] » Thu, Dec 09, 2021, 7:21 PM UTC

gherkinnn wrote: post #14

awestroke wrote: post #6

Since I learned to write semantic class names, and to compose using scss or react components, Tailwind feels like it would be a big step back. I get that it would be kind of nice to prototype in, but is anybody here using it for complex apps or UIs?

It feels strange at first but then it's a bit like flying.

[deleted]

Re: Tailwind CSS v3.0

#17

Post by gnabgib » Thu, Dec 09, 2021, 7:22 PM UTC

loeg wrote: post #8

(Formerly: dupe of https://news.ycombinator.com/item?id=29501125 . The comments have now been merged.)

Other one is actually the dupe (posted slightly later, and a poor URL choice), but has gained more traction

Re: Tailwind CSS v3.0

#18

Post by yurishimo » Thu, Dec 09, 2021, 7:23 PM UTC

awestroke wrote: post #6

Since I learned to write semantic class names, and to compose using scss or react components, Tailwind feels like it would be a big step back. I get that it would be kind of nice to prototype in, but is anybody here using it for complex apps or UIs?

Funnily, I've experienced something of the same, but inverted. I was all in on semantic class names for years, then moved over to Tailwind for a few work projects and couple of years.

Now I'm back working on a project with a team that is staunchly against TW and I'm having a hell of time getting back into the rhythm of naming things. Everything just kinda looks like a box so I'm having to go back to the the designer or team to pull out names for things.

Definitely looking forward to when I can go back to using Tailwind at work and on personal stuff. The cognitive overhead is real.

Re: Tailwind CSS v3.0

#19

Post by 1_player » Thu, Dec 09, 2021, 7:23 PM UTC

Before you ask, as it happens in every Tailwind post, what is the point of this when CSS "promotes" reuse and separation of concerns, have a look at @ 5e92cb50239222b comment: https://news.ycombinator.com/item?id=29501650

And let me repeat what every Tailwind fanboy (like me) states every time this project is on HN: don't knock it till you've tried it. Look at the animated example in the front page. You'll never be able to iterate that quickly with CSS.

Re: Tailwind CSS v3.0

#20

Post by pineconewarrior » Thu, Dec 09, 2021, 7:24 PM UTC

awestroke wrote: post #6

Since I learned to write semantic class names, and to compose using scss or react components, Tailwind feels like it would be a big step back. I get that it would be kind of nice to prototype in, but is anybody here using it for complex apps or UIs?

Netflix.

Also, you can prototype your stuff and then use the "extract" functionality to create components with nice shiny class names.