Classic rock, Mario Kart, and why we can’t agree on Tailwind • Hacker News Board

Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind

#41

Post by emmacharp » Wed, Sep 27, 2023, 1:22 PM UTC

alan_n wrote: post #27

I'm glad the writer has actually tried Tailwind and I respect it's not really their thing, but I've got to hard disagree with the Builder vs Crafter/specialist look on it. Tailwind will only just barely save you from not knowing CSS, it's still fundamental to understand it. Also I would consider myself very well versed in CSS, but while my handcrafted css works, it cannot compare in maintainability to its tailwind eq…

> CSS inevitably becomes a spaghetti soup of states after a while.

Not if you lint your CSS with rules preventing these kind of things. The same is true for maintainability. Stylelint is a great tool for that.

Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind

#42

Post by andrei_says_ » Thu, Sep 28, 2023, 7:40 AM UTC

yowzadave wrote: post #23

city41 wrote: post #10

I've been working in CSS for over 20 years. I know it very well. Tailwind is also my absolute most favorite technology to come along in a long time. I would even argue to use it effectively you also need to understand CSS well. The smart steering analogy doesn't jive with me at all.

Same--Tailwind is granular enough that nearly anything that can be done in CSS, can be done with Tailwind (with the caveat that Tailwind encourages you to use standard dimensional increments, which is usually a good idea anyway). IMO, Tailwind is a coping strategy for people who have accepted that CSS is bad technology. The Cascade seemed like a good idea at the time, and made for some cool demos back in the "CSS Zen…

In my experience well organized cascade is amazingly efficient (ITCSS approach) and standardizing of spacing, colors and typographic scale is trivial.

Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind

#43

Post by andrei_says_ » Thu, Sep 28, 2023, 7:45 AM UTC

rawfan wrote: post #26

timeon wrote: post #14

Earlier quoted context omitted.

> use Tailwind first and hand craft the small percent of CSS where that’s required later What is the difference between Tailwind and in-line CSS?

Inline styles have no support for media queries, container queries pseudo classes (hover, focus), pseudo elements (before) and attribute selectors. With tailwind I can even just stack them like this "lg:hover:px-[10px]".

Note that similarly to writing inline classes, if you need to refactor the css, you’d need to re-read and rewrite the class soup everywhere in your project.

Re: Classic rock, Mario Kart, and why we can’t agree on Tailwind

#44

Post by esher » Thu, Sep 28, 2023, 12:48 PM UTC

This speaks my heart. Lately I was asked by my team to ditch my own little CSS framework in favor of Tailwind CSS. Beside having an ego problem with it, I'd like to disable 'Smart Steeting' to take shortcuts now.

Shameless blog link: https://medium.com/teutonic-css/retiring-my-own-little-css-f...