Live data from Hacker News

NeutralinoJS: Lightweight Electron alternative using native browser controls

neutralino.js.org

1–10 of 200 posts

Re: NeutralinoJS: Lightweight Electron alternative using native browser controls

#5

So if I understand right, what makes this lighter than electron is the fact that only webkit2 is used instead of embedding the whole chromium app.

I don't understand, it seems like it runs in any browser? Are they using webkit2 as a replacement for node and the system browser for the GUI?

Re: NeutralinoJS: Lightweight Electron alternative using native browser controls

#6
post #5

So if I understand right, what makes this lighter than electron is the fact that only webkit2 is used instead of embedding the whole chromium app.

I don't understand, it seems like it runs in any browser? Are they using webkit2 as a replacement for node and the system browser for the GUI?

I agree that they really need to explain this better on their site somewhere.

Re: NeutralinoJS: Lightweight Electron alternative using native browser controls

#7
post #5

So if I understand right, what makes this lighter than electron is the fact that only webkit2 is used instead of embedding the whole chromium app.

I don't understand, it seems like it runs in any browser? Are they using webkit2 as a replacement for node and the system browser for the GUI?

It seems to me that the Javascript runs in the client.

The Javascript side calls the system via the local network, passing through this router: https://github.com/neutralinojs/neutralinojs/blob/master/cor...

I hope that there is some form of authentication to make sure no random web apps are accessing the API.

Re: NeutralinoJS: Lightweight Electron alternative using native browser controls

#8

So if I understand right, what makes this lighter than electron is the fact that only webkit2 is used instead of embedding the whole chromium app.

Indeed I think they don't ship the whole browser package.

What they might actually do is to locally launch a HTTP server which renders the app if you call it on any browser (localhost:8080 in the examples). The chrome of the app is actually a thin layer that use the default OS web browser. That is why the memory footprint is much less higher that alternatives like electron.

Post reply on HN