3 ms·
They could use NW.js instead, which stays up-to-date with the latest Chromium version, including security updates. They usually release on the same day as Chrom
by polpo 9y ago
They could use NW.js instead, which stays up-to-date with the latest Chromium version, including security updates. They usually release on the same day as Chromium. https://nwjs.io/blog/ https://nwjs.io/blog/
- orange8 9y agoGood answer. Some are just good at putting down solutions, and don't even have the courage to suggest alternatives.
- baby 9y agoThis is interesting, I feel like NW.js has lost the war against Electron, but I haven't closely been following the topic. Can anyone summarize the latest common opinion on the subject?
- orange8 9y agoI suspect most electron devs haven't even heard of NW.js even though it came first, so there wouldn't even be any comparison to begin with.
- polpo 9y agoThere was a period in late 2014-early 2015 where NW.js stagnated, but since then it's been very actively developed. I found this 2016 comparison pretty even-handed and comprehensive; it'd be nice to see an updated version for 2017. http://tangiblejs.com/posts/nw-js-and-electron-compared-2016-edition http://tangiblejs.com/posts/nw-js-and-electron-compared-2016...