You mean like those "Works in IE/Chrome" standards?

I am yet to see the huge ecosystem for Web components that matches component libraries like those from DevExpress or ComponentOne.

You have to actively ignore the web's landscape in the past 5-6 years to state something like this.

Lately, major vendors (with Edge, that includes Microsoft) are agreeing on standards, developing them FAST, and the web moves forward faster than it has ever moved. Long gone are the days where your standards can get stopped for multiple years. And vendor prefixes are less prevalent now as features get implemented properly sooner.

Really?

https://ishoudinireadyyet.com/

https://www.webcomponents.org/

https://hangouts.google.com/

Also, to use those standards, one needs to have access to latest browser versions, which never happens beyond controlled environments.

So typical web development always needs Modernizr, Babel, Polyfills (when possible) around.

The vast majority of current web development project don't need to go anywhere near the bleeding edge "still in development" browser APIs.

Your argument makes no sense in the year 2018.

Depends, if they are trying to compete with native apps or not.

Of course if they just stick with the ideal model of hypertext documents, with a little bit of JS, it doesn't make sense.

As for web apps, I am ok with them, provided they run on the browser I have already installed, instead of faking native apps.

Hey, some of us are still out here having to support IE 7... Glaciers move faster these days than some corporate clients.

And yet, I still frequently run into web applications that only run in Chrome. Mostly COTS enterprise products.

You have extra word in your second point. There is norhing mature. If anything webtech rushes implementation of some feature just so the checkbox “we can do it too” is ticked and that’s it.