If Web Components are so great, why am I not using them?
The main reason is that they&#x27;re too low-level to use directly.<p>They do a lot, but stop just short of being useful without something of a framework on top.  I tried hard to use them directly, but found that it was untenable without sensible template interpolation, and without helpers for event binding.<p>Here&#x27;s my shot at the smallest possible &quot;framework&quot; atop Web Components that make them workable (and even enjoyable) as an application developer:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;dchester&#x2F;yhtml">https:&#x2F;&#x2F;github.com&#x2F;dchester&#x2F;yhtml</a><p>It&#x27;s just ~10 SLOC, admittedly dense, but which make a world of difference in terms of usability.  With that in place, now you can write markup in a style not too dissimilar from React or Vue, like...<p><pre><code>    &lt;button @click=&quot;increment&quot;&gt;${this.count}&lt;&#x2F;button&gt;
</code></pre>
Whereas without, you need to bind your own events and manage your own template interpolation with sanitizing, handling conditionals, loops, and all the rest.<p>If we could get something in this direction adopted into the spec, it would open up a lot of use cases for Web Components that it just can&#x27;t address as-is.