NeutralinoJS: Lightweight Electron alternative using native browser controls

Post by zelly » Wed, Feb 26, 2020, 7:17 PM UTC

derefr wrote: post #48

I feel like nobody cares too much if they’re running one Electron app; people do have the headroom for an extra 1-2GB of RAM usage. The problem comes when they run several Electron apps at once, and each comes with its own “base” overhead (i.e. the runtime memory consumption of the browser-runtime as a whole, independent of how many render contexts are open.) Chromium is built to share a lot of things between tabs ef…

Post by pjmlp » Wed, Feb 26, 2020, 7:30 PM UTC

strbean wrote: post #95

pjmlp wrote: post #58

Earlier quoted context omitted.

We still need to support IE 11 on our projects anyway. Welcome to the corporate world.

Not if you are shipping chrome with your application. Isn't that part of the point of electron?

Post by pjmlp » Wed, Feb 26, 2020, 7:33 PM UTC

spenvo wrote: post #87

pjmlp wrote: post #16

This is the correct way of doing it when a PWA doesn't cut it. No need to push a full browser engine when the OS already has enough of them available.

What are the top reasons an PWA wouldn't cut it?

Post by ArtifTh » Wed, Feb 26, 2020, 7:43 PM UTC

zelly wrote: post #101

derefr wrote: post #48

I feel like nobody cares too much if they’re running one Electron app; people do have the headroom for an extra 1-2GB of RAM usage. The problem comes when they run several Electron apps at once, and each comes with its own “base” overhead (i.e. the runtime memory consumption of the browser-runtime as a whole, independent of how many render contexts are open.) Chromium is built to share a lot of things between tabs ef…

Given that everyone brings this up every time Electron is mentioned, and Electron apps keep proliferating, I expect a future version of Windows and macOS to have Chromium bundled with the OS. There will be some platform independent open standard that Electron will use under the covers. Native desktop apps are never coming back. It will either be Electron or mobile apps emulated on desktops.

Post by andai » Wed, Feb 26, 2020, 8:00 PM UTC

hnuser123456 wrote: post #81

csnover wrote: post #64

Earlier quoted context omitted.

I’m currently running three Electron apps: Spotify, Skype, and VS Code. Spotify: 1083.7 MB. VS Code: 890.9 MB. Skype: 406 MB. In the past, I’ve had projects open in VS Code which have caused that number to shoot up into the multi-gigabyte range. Of course this is all anecdotal but I am pretty sure these numbers come from actual experiences that people are having with Electron apps.

Keybase also uses in the range of 600MB-1GB, and 8 processes, most of which don't exit when you exit the application. I'm not sure what Discord uses because I only run it in the browser, but I'm sure it's in the same range as all of the above. I've come up with a powershell snippet to fully quit keybase and reclaim ~1GB RAM: get-process | Where-Object {$_.path -match "keybase"} | Stop-Process