Conversation

Notices

1. jenny (phire) (phire@phire.place)'s status on Tuesday, 07-Mar-2023 16:04:00 JST jenny (phire)

   TIL about DaisyUI, a component library that wraps Tailwind utility classes into common patterns and you guys, that's just CSS, I'm begging you to just write some CSS

   • Adrian Cochrane (alcinnz@floss.social)'s status on Tuesday, 07-Mar-2023 16:24:33 JST Adrian Cochrane

     in reply to

     @phire I really struggle to understand how Tailwind is any different than using the `style` property...

     O.K., there's some enhancements. Nothing that can't be accomplished using CSS Variables, that's a thing now!

     And with CSS Cascade Layers there should be no reason to fear the Cascade, a fear which led to Tailwind being created!

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 08-Mar-2023 08:31:59 JST Adrian Cochrane

     in reply to

     • gotofritz

     @gotofritz @phire I'll concur to the extent that it would've been better if we could've gotten more predictability over this sooner... But you know what they say about hindsight!

     What I defend is having a separation between semantics & style, since that allows your pages to be displayed in unexpected places. As long as we have the separation the cascade helps make it more predictable!

   • gotofritz (gotofritz@fosstodon.org)'s status on Wednesday, 08-Mar-2023 08:32:00 JST gotofritz

     in reply to

     • Adrian Cochrane

     @alcinnz @phire the cascade was always a terrible idea, not sure why CSS people have such a fetish for it. In any other programming language having a "unit of code" change behaviour in unexpected way if you put it in a different context would be considered a major fail

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 08-Mar-2023 08:40:50 JST Adrian Cochrane

     in reply to

     • gotofritz

     @gotofritz @phire I still struggle to understand how Tailwind is any different to the CSS `style` attribute... Or any easier to learn...

   • gotofritz (gotofritz@fosstodon.org)'s status on Wednesday, 08-Mar-2023 08:40:51 JST gotofritz

     in reply to

     @phire But we like it that way. Not everybody likes or wants to have to deal with CSS

     By sheer coincidence I just posted a Douglas Adams quote that will fit perfectly

     https://fosstodon.org/@gotofritz/109978439521357104

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 08-Mar-2023 08:43:12 JST Adrian Cochrane

     in reply to

     • gotofritz

     @gotofritz @phire Fair enough!

   • gotofritz (gotofritz@fosstodon.org)'s status on Wednesday, 08-Mar-2023 08:43:14 JST gotofritz

     in reply to

     • Adrian Cochrane

     @alcinnz @phire I don't know, I guess it depends on the application. If you focus is the information (say, Wikipedia, or a government agency site, that kind of thing - basically anywhere you'd use the site even if it didn't have any CSS) then I would agree.

     But in my work experience (design agencies back in the day, startups later) there were never any benefits. It was fundamentally design work, driven by typograhy, not semantics. With constant redesigns. Too much semantics only got in the way

   • Adrian Cochrane (alcinnz@floss.social)'s status on Wednesday, 08-Mar-2023 08:55:41 JST Adrian Cochrane

     in reply to

     • gotofritz

     @gotofritz @phire For me it's more bemusement. Though I don't trust the mindset it reinforces to create pages which sound decent in my auditory browser.

     Personally my goto for most of the benefits of Tailwind would be Simple.CSS & the `style` attribute.

     Because I do admit that the CSS defaults are stuck back in the day of standard-resolution desktop monitors, due to backwards compatibility. CSS frameworks have a place, it's just rare to find one I like.

   • gotofritz (gotofritz@fosstodon.org)'s status on Wednesday, 08-Mar-2023 08:55:42 JST gotofritz

     in reply to

     • Adrian Cochrane

     @alcinnz @phire

     An example I was dealing with the other day: a grid was getting squished because it was declared as 1fr 1fr, which is interpreted as minmax(auto, 1fr). Tailwind's grid under the bonnet use minmax(=, 3fr). As a user that complexity is hidden away from you, you just define a 4 columns grid.

     What gets me is the _hatred_ I sometimes see in the CSS communit for it. It's just a a library, use it if you like or don't if you don't... 🤷♂️

   • gotofritz (gotofritz@fosstodon.org)'s status on Wednesday, 08-Mar-2023 08:55:44 JST gotofritz

     in reply to

     • Adrian Cochrane

     @alcinnz @phire one reason is that it picks sensible defaults for you. You can do next to nothing and your UI will look 'decent'. It's a reasonable subset of CSS that JustWorks and papers over the oddities. Basically what jQuery used to be for JS

     Adrian Cochrane repeated this.