Earlier quoted context omitted.
I haven't seen cascades be a problem since the days of monolithic, app-wide stylesheets, and no project I personally know of works that way anymore. Just about everyone uses component-specific styles with a limited set of selectors where there are very few collisions per property, and pretty clear specificity winners when there are. If the alternative to the cascade is that you have to repeat granular style choices o…
> Just about everyone uses component-specific styles Yeah. At which point you can simply use e.g Tailwind.
With plain CSS components can easily share styles and use them by adding the correct class name to elements.
With Tailwind you have to copy your list of super fine-grained classes to each component, and try to keep them in sync over time