Don't forget there are many unpopular (wdsl) and dead (xhtml, e4x) standards out there already. There is absolutely no reason to believe that web components will have a better track record.
Of course there're reasons to believe it: Web Components solve some critical problems, All the browsers are in support of the standards and implementing them, we've had very good uptake with Polymer, other Web Component frameworks are popping up at places like Atlassian, and many large companies like ING, IBM, GE, Bloomberg, Salesforce, and of course Google - with YouTube and more - moving to Web Components.
Relevant to this discussion, Web Components will make it possible for less mainstream frameworks to get a foothold in real applications by not being locked out by proprietary silos.
Well, realistically speaking, web components consist of a bunch of different specs and each specification should really be considered on its own merits. Shadow DOM and Custom Elements are mostly ok. HTML Imports spec looks like it was created with the simple "include jQuery widget on the page" use case in mind and doesn't consider anything else. Node.js/npm/CommonJS ecosystem, es6 modules — it's like nothing of this even exist. This is obviously not good enough and that's why Mozilla decided to not support this thing.
> being locked out by proprietary silos
That's a really mean thing to say about an open-source javascript library. Especially considering that Inferno is a reimplementation of React API. I actually think Fb should make React API into its own mini-spec (like JSX or GraphQL) if only for trolling "muh web standards!" people.
