K
K
KnightForce2016-02-22 17:27:10
JavaScript
KnightForce, 2016-02-22 17:27:10

NW.js vs Electron?

To write desktop applications using web technologies, which is better to use, NW.js or Electron?
What are the pros and cons?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
L
lem_prod, 2016-02-22
@lem_prod

In terms of performance, they do not differ much, the compiled programs will take up approximately the same amount of memory, it’s more a matter of taste, NW.js is connected via package.json with the main *.html file, to which the configuration *.js is connected, I think everything is so if my memory does not fail me, in elecnton the connection is also through *.json but refers directly to the configuration *.js, which in turn opens windows, etc.
roughly speaking, in NW.js the main .html file, and in Electon.js
I don’t remember the features of the first one, but I got acquainted with both platforms at the same time, and Electron seemed to me an order of magnitude more logical, so I chose it, but purely theoretically, one and the same functionality can be implemented both there and there.

S
s2dent, 2016-03-03
@s2dent

The main (but far from the only) distinguishing feature in them is the approach to implementation. In NW, the entry point can be HTML or JS, while Electron has a javascript entry point that starts separate processes for application windows, i.e. for each new window new processes will be born.
You can read more here .

A
Alexander Sigmanor, 2016-02-22
@sigmanor

As for me, it's a matter of taste, you can read about the main changes in the electron docks

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question