[SquareWheel]

I'm a big fan of Harry's, and I've been hoping to see him publish more details on ITCSS. I built my current website around the methodology based on a talk he gave years ago. When last I checked though, there still weren't any readily-available details or documentation on the topic.

With the prevalence of component frameworks though, and certain new technologies like CSS Layers and :where(), I feel ITCSS may not be as essential as it used to be. Specificity is becoming less of a problem to manage for large-scale websites. I think it still has its place, but is maybe not the universal solution I once saw it as.

[lelandfe]

Between ITCSS, SMACSS, BEM, and all the other CSS naming and structural conventions, it's been pretty nice to do CSS-in-JS and not really worry about the cascade.

[toastal]

Except not all sites need or should really use JS

[ponyous]

You can use CSS in JS on server side only, and serve it as a normal html + css site to a browser.

[andrei_says_]

ITCSS model helped me dramatically reduce the amount of css I write.

Also, Harry has a class on Skillshare.

[handonam]

Absolutely this!

I did a migration/update of a site using this idea (before styled-components became the norm), and it was just insane how much CSS was saved. The new design was AT MOST half the size of the original.