Let me explain the argument to you: > You can always add another layer of abstraction to solve a problem but removing one can be difficult. The argument being

Let me explain the argument to you: > You can always add another layer of abstraction to solve a problem but removing one can be difficult. The argument being that there's no need to add anything to the browser stack and make it even more complex when it doesn't add any essential capability. There's already JS making everything possible; and yet, they keep on piling stuff. When with custom elements specifically, you also require JS anyway (to declare them). > Elements are not components. Idk maybe for "web devs" the concept is difficult to grasp that HTML isn't for them. It's for text authors, and as such a markup vocabulary where low-level elements are placed next to complex custom controls nilly-willy isn't really a useful evolutionary direction.