A handful of benefits:

1. Specificity - swim-line.buttons vs .swin-lines.buttons vs .buttons.swim-lanes. 2. Future pathing - Maybe you don't need a Web Component today, but you might need one tomorrow. 3. Cleaner - <swim-lane /> is just better than <div class="swim-lane" />

▲

pier25 9 hours ago | parent | next [-]

> Specificity

:where() gives you zero specificity.

> Future pathing

Sounds like premature optimization. And I say this as someone who has been using custom elements and web components in production since 2016. In fact one of my products offers WCs for our customers:

https://docs.wavekit.app/web-components-wavekit-audio/

> Cleaner

Debatable. Personally I find it cleaner to simply rely on CSS to solve something rather a combination of CSS, JS, and some custom markup.

▲

etchalon 8 hours ago | parent [-]

1. ... I do not understand what you mean.

2. One person's "premature optimization" is someone else's "this was literally something I dealt with this week."

3. This method relies on CSS and HTML, just as any other styling solution would.

	▲	grodriguez100 3 hours ago \| parent [-]
		2. Yet it was you who said “future” in the first place…

▲

smrq 11 hours ago | parent | prev [-]

"Clean" is the biggest lie in software development. It's an aesthetic opinion dressed up as objective fact. You think components are clean, someone else thinks classes are clean, and neither of you are wrong, except for believing that "clean" is a property of the code and not something entirely in your own mind.

	▲	etchalon 8 hours ago \| parent [-]
		I'm going to start using this logic whenever my wife talks about my office.