News for hackers. Stuff that matters.
Re:Doing work locally minimizes problems with Electron apps by wlesieutre on Tuesday June 25, 2019 @11:06AM (#20274963)
Electron ships its own Chromium-based browser view. Using the OS provided one does sound like an efficient option, but then you have to deal with all the same compatibility testing (different browsers, different releases, running under different OSes and OS releases) that makes web development suck. It's trying to provide a web-based stack while abstracting away most of those headaches.

It also provides some Chrome specific functionality (loading Chrome extensions) that wouldn't work in an engine-agnostic system, though I don't imagine this is a commonly used mechanism. Extensions are more useful for shoving your own functionality into someone else's webpage, if you control the whole codebase surely it's not the best way to do anything.

https://electronjs.org/docs/api/browser-window#browserwindow...

Re:Doing work locally minimizes problems with Electron apps by monksy on Tuesday June 25, 2019 @11:16AM (#20275066)
> but then you have to deal with all the same compatibility testing

Which means they choose the wrong way to go about creating an app. If you have to bundle a huge secondary app just to run your main application, you've done something wrong.

Re:Doing work locally minimizes problems with Electron apps by coldtea on Tuesday June 25, 2019 @01:28PM (#20276620)
If you have a multi-billion valuation while doing it, and millions of users, you could not care less...