3 ms·

I understand the motivation for wanting to avoid frameworks when it looks like a native solution is right around the corner, but that’s just it – it’s not here

I understand the motivation for wanting to avoid frameworks when it looks like a native solution is right around the corner, but that’s just it – it’s not here yet. There isn’t even experimental support for Web Components in either the most popular desktop browser or the most popular mobile browser, and the polyfills are simply nowhere near as mature or well-supported as React and Angular are for the same purposes. So yes, you could develop for Web Components today, and it would “work” everywhere and it would be the platonic ideal of future-proof web development. It just wouldn’t be very pragmatic.

nostrademons 12y ago
Chrome's the most popular desktop browser [1], and Chrome for Android is the most popular mobile browser [2]. [1] http://en.wikipedia.org/wiki/Usage_share_of_web_browsers http://en.wikipedia.org/wiki/Usage_share_of_web_browsers [2] http://caniuse.com/#search=shadow%20dom http://caniuse.com/#search=shadow%20dom It passed IE for desktop in mid-2012, and iOS Safari for mobile in late 2012 or early 2013. I agree with your general point since the all Webcomponents-supporting browsers are barely a majority. But the web looks very different from it did even a couple months ago.