In theory, yes, but in practice it's a different story. Early on in a project's life, avoiding these pitfalls is easy. But as a project grows both in team and c

In theory, yes, but in practice it's a different story. Early on in a project's life, avoiding these pitfalls is easy. But as a project grows both in team and codebase size, those quick CSS hacks to get some functionality out the door accumulate. After some time, you will begin to run into issues where some components in the tree aren't rendering the way you expect because some other component(s) are applying styles using a selector that may have worked at the time, but is now too broad. Even if your app is 100% CSS in JS, though easier to avoid, you may run into these issues. I'm all for this feature.