The tension is between two kinds of CSS users. The ones who want cascading style sheets, and the ones who want scoped style sheets. And sometimes even people who think they want scope find out they also want the cascade, and just wanted to scope a bit "at the end" (something the cascade can do anyway)
replyScoping now is much easier with CSS Modules
replyYou can also literally scope things between X and Y now (with @scope)
replyI find that developers add a CSS reset without thinking about it as if there is always a need. We never used resets. There was never a need. Typically we would set something according to the design anyway and starting with a reset was like slamming something against one wall only to throw it back to a different wall later.
replyThey were a lot more necessary when each browser threw in fairly random sets of default styling. These days they've converged heavily on the same defaults.
replySurely you must reset something? At the very least box-sizing
replyThe box-sizing property is another way of calculating element sizes but not the default way or the only way. Those of us who were adept at calculating the area sizes after years of doing so had no need for it. Those who are new to the game or can't figure it out use box-sizing.
replyAnd don't call me Shirley
The history here, as I understand it, was that they imagined you would use custom elements from multiple third parties, so any shared CSS definitions would cause breakages.
replySee eg the (now removed) HTML imports standard.