Notices by gotofritz (gotofritz@fosstodon.org)

@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

@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... 🤷♂️

@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

@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

@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