Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing NW.js (w/xvfb) vs Proton native, the Slant community recommends NW.js (w/xvfb) for most people. In the question“What are the best tools for building cross-platform desktop apps with web technologies?” NW.js (w/xvfb) is ranked 2nd while Proton native is ranked 9th. The most important reason people chose NW.js (w/xvfb) is:
The integration of Node with the DOM in NW.js opens up a number of new options in how your headless testing workflow can be facilitated. The distinct separation of JavaScript contexts, the introduction of a separate node context, and the ability to cross communicate, offers a lot of power and flexibility.
Specs
Question Ranking
Pros
Pro Node integration
The integration of Node with the DOM in NW.js opens up a number of new options in how your headless testing workflow can be facilitated.
The distinct separation of JavaScript contexts, the introduction of a separate node context, and the ability to cross communicate, offers a lot of power and flexibility.
Pro NaCl support/integration
Access to the Native Client offers up more options in implementing your testing workflow.
Pro Open source
Pro Uses native tools
Not running a browser to manage the GUI, it uses less resources than the alternatives.
Pro No chromium
Is not based on chromium.
Cons
Con xvfb Requirement (for now)
Headless is on the NW.js roadmap, but for now xvfb is necessary to get going. The community has done the work and you can find the details here.
Con Not popular
Not being popular as electron js, its development isn't quite at the same pace.
Con No styling
Being based on libui, CSS styling isn't available.
