We start by not shipping Chrome with "native" applications instead of learning the platform APIs.

Followed by creating Web applications based on Web standards, instead of whatever Chrome does, and then complain about Firefox and Safari not being up to the game.

▲

franga2000 4 hours ago | parent [-]

I really don't see how Electron is connected here. When you're an Electron app, you really don't have to care about which web APIs Chrome implements, you can just use the native NodeJS equivalents, which will usually give you a better UX anyways.

But absolutely on the second point. A standard with one implementation is not a standard. Regardless of market share, in a market with three providers, if two out of three don't support something, you have no business using it. It unhealthy for everyone involved.

▲

pjmlp 3 hours ago | parent [-]

Electron is Chrome packaged with the application.

If those devs cared about Web standards, it would be a pure Web application, or an headless executable, system/daemon conecting to the system's browser.

▲

franga2000 3 hours ago | parent [-]

I'm not saying the Electron UX is better than a native app. I'm saying Electron apps using NodeJS libs have better UX to Electron apps using Web APIs. At best there's no difference for the user, but at worst, they get permission popups and limited access just like they would in a browser.

This is why Electron app devs prefer NodeJS libs to Web APIs and consequently have no impact on the adoption of a large chunk of the new Web APIs (not counting DOM and CSS things because those are rarely controversial and usually broadly implemented).

So yes, those devs don't care about these kinds of new web "standards", because they don't work with them. The people who use them are the ones who are dangerous and that's almost exclusively web app authors, because they can't just pull in a native library to do the same things.

	▲	pjmlp 3 hours ago \| parent [-]
		Which browser engine uses V8?