3 ms·
Right. Also each Electron app "comes with a copy of two large software frameworks, Node.js and Chromium" ( https://medium.com/dailyjs/put-your-electron-app-on-a
by galaxyLogic 6y ago
Right. Also each Electron app "comes with a copy of two large software frameworks, Node.js and Chromium"
( https://medium.com/dailyjs/put-your-electron-app-on-a-diet-with-electrino-c7ffdf1d6297 https://medium.com/dailyjs/put-your-electron-app-on-a-diet-w... )
Whereas if you build starting from Node.js (or Deno I assume) you can skip the Chromium part. Instead of packaging Chromium with your app you assume that users have a browser and can use that to talk to your app.
The benefit of using Node.js is you don't have to use a different language for the backend. It helps.
BTW. "Electrino" in the linked-to article seems interesting too.
- feanaro 6y agoThe additional benefit of this approach is that you can then build your application such that it works with all standards-compatible browsers, such as Firefox.
- yboris 6y agoThat's not a benefit - that's a down-side. When writing a front-end for Electron, you only worry about 1 browser and you have a guarantee that it will work the same way across every OS. If you have to write a front end (website) that works with more browsers, you have to put in moro work.
- feanaro 6y agoIt's a benefit from the point of view of the user and for the openness of the web. We shouldn't rely on features exclusive to a single browser anyway.