The big takeaway here is interoperability. React is great, Angular was great for its time, etc, but if your company builds out all its UI components in a specific framework you're locked into that framework, so a lot of churn happens if you ever decide to try the newest hotness. It appears that all the major browser vendors are now in agreement on a Web Components spec so it's only a matter of time now before we have a good, standardized way of extending the web spec.
Google cache: <a href="http://webcache.googleusercontent.com/search?q=cache:O7S2IstQexsJ:https://queue.acm.org/detail.cfm%3Fid%3D2844732+&cd=1&hl=en&ct=clnk&gl=us" rel="nofollow">http://webcache.googleusercontent.com/search?q=cache:O7S2Ist...</a>
There is no solution here. Who decides what I can and cannot declare with the select? If it's not me, then how will this other body of control make sure to include all possibilities in their API, which satisfy my requirements that even I don't know yet? And of course, how will these features work together? and then also be efficient?<p>.. aaaand we're back to where we are today. Pointless article.